Public report of mahedee/code-sample02, 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, 04:32 UTC · Survey ID cd_19ad5bdc1f54431d88f757e03edd9358
mahedee/code-sample02
Measured 22 October 2026, 04:24 UTC, at code version b29b565
CAI scoreProvisionalDown 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 32,360 lines of product code in 104 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Maturity, 29
Findings by how serious they are
238 critical1043 serious471 minor
5 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, 04:24 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 4 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: CS1031: Type expected; CS1001: Identifier expected; CS1003: Syntax error, ',' expected
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 ▸
110of 115 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
1726of 1752 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
115dimensions across 10 lenses, read from 32,360 lines of product code in 104 projects.
mahedee/code-sample02 scores 34 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.
The weakest lens counts most in the score, and here that is Maturity, which scores 29 and is rated Weak. Its Knowledge Freshness dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to expand the README with getting-started, architecture overview and a project map and to record your significant design decisions, and if Maturity rose to 70, the score would rise from 34 to about 38.
238 findings are critical: 96 in Dependency Vulnerabilities, 42 in Explicit Debt, 26 in IaC & Container Security, 25 in REDACTED Scanning, 20 in Forms & labels, 20 in Secrets (history), three in Immutable events, two in Test Quality, one in Dependency Hygiene, one in Outbox / dual-write, one in Project dependency cycles and one in Web-Security Posture.
Watchdog couldn't measure 4 dimensions in this code, among them Code Coverage, Dependency Hygiene and IL Efficiency, so they are left out of the score. The product code is 32,360 lines, which would take an estimated 0.3 person-years, around €51,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Maturity rose from 29 to 70, the lowest score rated Strong, the score would rise from 34 to about 38.
Code composition: what the lines of code are
Business logic 11%Supporting code 66%Tests 2%Generated by tools 21%
New since the last survey: 358 findings
These 358 critical or serious findings weren't in the previous survey, on 7 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
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: 45 findings
These 45 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.
One transaction, one aggregate · One operation mutates 2 aggregates: CustomerRepository.UpdateAsync DapperDemo/DapperDemo/Customer.API/Repositories/CustomerRepository.cs
Async & latency hygiene · Awaits without ConfigureAwait(false)
Rebuild cost: about €51,000 · Estimate
Cost to rebuild
€17,000 to €85,000, for 284 to 892 hours of work, about 0.3 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 34. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 32,360 lines of product code
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
Expand the README with getting-started, architecture overview and a project map.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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: CS1031: Type expected; CS1001: Identifier expected; CS1003: Syntax error, ',' expected
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €51,000 to build again, about 0.3 person-years of work. Its weakest lens is Maturity, at 29 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
One cause behind 24 Domain Modelling findings · Common cause
24 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 (8 findings) · Rich vs anemic model (8 findings) · Strongly-typed ids (8 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 — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
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.
310 modules, with 275 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 270 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.
Application.Common.Interfaces uses Domain.Entities, so a change to Domain.Entities can break Application.Common.Interfaces, while a change to Application.Common.Interfaces can't break Domain.Entities.
Position
Below the diagonal: Application.Common.Interfaces uses a module listed above it, which is the healthy direction.
AuditLog.API.Persistence uses AuditLog.API.Models, so a change to AuditLog.API.Models can break AuditLog.API.Persistence, while a change to AuditLog.API.Persistence can't break AuditLog.API.Models.
Position
Below the diagonal: AuditLog.API.Persistence uses a module listed above it, which is the healthy direction.
AuditLog.API.Repositories.Interfaces uses AuditLog.API.Models, so a change to AuditLog.API.Models can break AuditLog.API.Repositories.Interfaces, while a change to AuditLog.API.Repositories.Interfaces can't break AuditLog.API.Models.
Position
Below the diagonal: AuditLog.API.Repositories.Interfaces uses a module listed above it, which is the healthy direction.
MTShop.Application.Common.Models uses MTShop.Core.Entities.Admin.Identity, so a change to MTShop.Core.Entities.Admin.Identity can break MTShop.Application.Common.Models, while a change to MTShop.Application.Common.Models can't break MTShop.Core.Entities.Admin.Identity.
Position
Below the diagonal: MTShop.Application.Common.Models uses a module listed above it, which is the healthy direction.
MTShop.Application.Common.Models uses MTShop.Core.Entities.Identity, so a change to MTShop.Core.Entities.Identity can break MTShop.Application.Common.Models, while a change to MTShop.Application.Common.Models can't break MTShop.Core.Entities.Identity.
Position
Below the diagonal: MTShop.Application.Common.Models uses a module listed above it, which is the healthy direction.
MTShop.Application.Interfaces uses MTShop.Core.Entities.Admin, so a change to MTShop.Core.Entities.Admin can break MTShop.Application.Interfaces, while a change to MTShop.Application.Interfaces can't break MTShop.Core.Entities.Admin.
Position
Below the diagonal: MTShop.Application.Interfaces uses a module listed above it, which is the healthy direction.
MTShop.Application.Interfaces uses MTShop.Core.Entities.Identity, so a change to MTShop.Core.Entities.Identity can break MTShop.Application.Interfaces, while a change to MTShop.Application.Interfaces can't break MTShop.Core.Entities.Identity.
Position
Below the diagonal: MTShop.Application.Interfaces uses a module listed above it, which is the healthy direction.
MTShop.Application.Interfaces.Admin uses MTShop.Core.Entities.Admin, so a change to MTShop.Core.Entities.Admin can break MTShop.Application.Interfaces.Admin, while a change to MTShop.Application.Interfaces.Admin can't break MTShop.Core.Entities.Admin.
Position
Below the diagonal: MTShop.Application.Interfaces.Admin uses a module listed above it, which is the healthy direction.
MTShop.Application.Interfaces.Admin uses MTShop.Core.Entities.Admin.Identity, so a change to MTShop.Core.Entities.Admin.Identity can break MTShop.Application.Interfaces.Admin, while a change to MTShop.Application.Interfaces.Admin can't break MTShop.Core.Entities.Admin.Identity.
Position
Below the diagonal: MTShop.Application.Interfaces.Admin uses a module listed above it, which is the healthy direction.
MTShop.Application.Interfaces.Repositories uses MTShop.Core.Entities, so a change to MTShop.Core.Entities can break MTShop.Application.Interfaces.Repositories, while a change to MTShop.Application.Interfaces.Repositories can't break MTShop.Core.Entities.
Position
Below the diagonal: MTShop.Application.Interfaces.Repositories uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Persistence.Admin uses MTShop.Core.Entities.Admin, so a change to MTShop.Core.Entities.Admin can break MTShop.Infrastructure.Persistence.Admin, while a change to MTShop.Infrastructure.Persistence.Admin can't break MTShop.Core.Entities.Admin.
Position
Below the diagonal: MTShop.Infrastructure.Persistence.Admin uses a module listed above it, which is the healthy direction.
Ordering.Core.Repositories.Query uses Ordering.Core.Entities, so a change to Ordering.Core.Entities can break Ordering.Core.Repositories.Query, while a change to Ordering.Core.Repositories.Query can't break Ordering.Core.Entities.
Position
Below the diagonal: Ordering.Core.Repositories.Query uses a module listed above it, which is the healthy direction.
Ordering.Infrastructure.Data uses Ordering.Core.Entities, so a change to Ordering.Core.Entities can break Ordering.Infrastructure.Data, while a change to Ordering.Infrastructure.Data can't break Ordering.Core.Entities.
Position
Below the diagonal: Ordering.Infrastructure.Data uses a module listed above it, which is the healthy direction.
AuditLog.API.Controllers uses AuditLog.API.Models, so a change to AuditLog.API.Models can break AuditLog.API.Controllers, while a change to AuditLog.API.Controllers can't break AuditLog.API.Models.
Position
Below the diagonal: AuditLog.API.Controllers uses a module listed above it, which is the healthy direction.
AuditLog.API.Controllers uses AuditLog.API.Persistence, so a change to AuditLog.API.Persistence can break AuditLog.API.Controllers, while a change to AuditLog.API.Controllers can't break AuditLog.API.Persistence.
Position
Below the diagonal: AuditLog.API.Controllers uses a module listed above it, which is the healthy direction.
AuditLog.API.Repositories.Implementations uses AuditLog.API.Models, so a change to AuditLog.API.Models can break AuditLog.API.Repositories.Implementations, while a change to AuditLog.API.Repositories.Implementations can't break AuditLog.API.Models.
Position
Below the diagonal: AuditLog.API.Repositories.Implementations uses a module listed above it, which is the healthy direction.
AuditLog.API.Repositories.Implementations uses AuditLog.API.Persistence, so a change to AuditLog.API.Persistence can break AuditLog.API.Repositories.Implementations, while a change to AuditLog.API.Repositories.Implementations can't break AuditLog.API.Persistence.
Position
Below the diagonal: AuditLog.API.Repositories.Implementations uses a module listed above it, which is the healthy direction.
AuditLog.API.Repositories.Implementations uses AuditLog.API.Repositories.Interfaces, so a change to AuditLog.API.Repositories.Interfaces can break AuditLog.API.Repositories.Implementations, while a change to AuditLog.API.Repositories.Implementations can't break AuditLog.API.Repositories.Interfaces.
Position
Below the diagonal: AuditLog.API.Repositories.Implementations uses a module listed above it, which is the healthy direction.
MTShop.Application uses MTShop.Core.Entities.Identity, so a change to MTShop.Core.Entities.Identity can break MTShop.Application, while a change to MTShop.Application can't break MTShop.Core.Entities.Identity.
Position
Below the diagonal: MTShop.Application uses a module listed above it, which is the healthy direction.
MTShop.Application uses MTShop.Application.Common.Models, so a change to MTShop.Application.Common.Models can break MTShop.Application, while a change to MTShop.Application can't break MTShop.Application.Common.Models.
Position
Below the diagonal: MTShop.Application uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Auth uses MTShop.Application.DTOs, so a change to MTShop.Application.DTOs can break MTShop.Application.Commands.Auth, while a change to MTShop.Application.Commands.Auth can't break MTShop.Application.DTOs.
Position
Below the diagonal: MTShop.Application.Commands.Auth uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Auth uses MTShop.Application.Interfaces, so a change to MTShop.Application.Interfaces can break MTShop.Application.Commands.Auth, while a change to MTShop.Application.Commands.Auth can't break MTShop.Application.Interfaces.
Position
Below the diagonal: MTShop.Application.Commands.Auth uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Auth uses MTShop.Application.Interfaces.Admin, so a change to MTShop.Application.Interfaces.Admin can break MTShop.Application.Commands.Auth, while a change to MTShop.Application.Commands.Auth can't break MTShop.Application.Interfaces.Admin.
Position
Below the diagonal: MTShop.Application.Commands.Auth uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Customer uses MTShop.Application.DTOs, so a change to MTShop.Application.DTOs can break MTShop.Application.Commands.Customer, while a change to MTShop.Application.Commands.Customer can't break MTShop.Application.DTOs.
Position
Below the diagonal: MTShop.Application.Commands.Customer uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Customer uses MTShop.Application.Interfaces, so a change to MTShop.Application.Interfaces can break MTShop.Application.Commands.Customer, while a change to MTShop.Application.Commands.Customer can't break MTShop.Application.Interfaces.
Position
Below the diagonal: MTShop.Application.Commands.Customer uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Customer uses MTShop.Application.Interfaces.Repositories, so a change to MTShop.Application.Interfaces.Repositories can break MTShop.Application.Commands.Customer, while a change to MTShop.Application.Commands.Customer can't break MTShop.Application.Interfaces.Repositories.
Position
Below the diagonal: MTShop.Application.Commands.Customer uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Products uses MTShop.Application.DTOs, so a change to MTShop.Application.DTOs can break MTShop.Application.Commands.Products, while a change to MTShop.Application.Commands.Products can't break MTShop.Application.DTOs.
Position
Below the diagonal: MTShop.Application.Commands.Products uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Products uses MTShop.Application.Interfaces, so a change to MTShop.Application.Interfaces can break MTShop.Application.Commands.Products, while a change to MTShop.Application.Commands.Products can't break MTShop.Application.Interfaces.
Position
Below the diagonal: MTShop.Application.Commands.Products uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Products uses MTShop.Application.Interfaces.Repositories, so a change to MTShop.Application.Interfaces.Repositories can break MTShop.Application.Commands.Products, while a change to MTShop.Application.Commands.Products can't break MTShop.Application.Interfaces.Repositories.
Position
Below the diagonal: MTShop.Application.Commands.Products uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Tenant uses MTShop.Application.DTOs, so a change to MTShop.Application.DTOs can break MTShop.Application.Commands.Tenant, while a change to MTShop.Application.Commands.Tenant can't break MTShop.Application.DTOs.
Position
Below the diagonal: MTShop.Application.Commands.Tenant uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Tenant uses MTShop.Application.Interfaces, so a change to MTShop.Application.Interfaces can break MTShop.Application.Commands.Tenant, while a change to MTShop.Application.Commands.Tenant can't break MTShop.Application.Interfaces.
Position
Below the diagonal: MTShop.Application.Commands.Tenant uses a module listed above it, which is the healthy direction.
MTShop.Application.Commands.Tenant uses MTShop.Application.Interfaces.Admin, so a change to MTShop.Application.Interfaces.Admin can break MTShop.Application.Commands.Tenant, while a change to MTShop.Application.Commands.Tenant can't break MTShop.Application.Interfaces.Admin.
Position
Below the diagonal: MTShop.Application.Commands.Tenant uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Implementations uses MTShop.Core.Entities.Admin.Identity, so a change to MTShop.Core.Entities.Admin.Identity can break MTShop.Infrastructure.Implementations, while a change to MTShop.Infrastructure.Implementations can't break MTShop.Core.Entities.Admin.Identity.
Position
Below the diagonal: MTShop.Infrastructure.Implementations uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Implementations uses MTShop.Core.Entities.Identity, so a change to MTShop.Core.Entities.Identity can break MTShop.Infrastructure.Implementations, while a change to MTShop.Infrastructure.Implementations can't break MTShop.Core.Entities.Identity.
Position
Below the diagonal: MTShop.Infrastructure.Implementations uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Implementations uses MTShop.Application.Interfaces, so a change to MTShop.Application.Interfaces can break MTShop.Infrastructure.Implementations, while a change to MTShop.Infrastructure.Implementations can't break MTShop.Application.Interfaces.
Position
Below the diagonal: MTShop.Infrastructure.Implementations uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Implementations uses MTShop.Application.Interfaces.Admin, so a change to MTShop.Application.Interfaces.Admin can break MTShop.Infrastructure.Implementations, while a change to MTShop.Infrastructure.Implementations can't break MTShop.Application.Interfaces.Admin.
Position
Below the diagonal: MTShop.Infrastructure.Implementations uses a module listed above it, which is the healthy direction.
Ordering.Application.Commands.Customers.Update uses Ordering.Application.DTOs, so a change to Ordering.Application.DTOs can break Ordering.Application.Commands.Customers.Update, while a change to Ordering.Application.Commands.Customers.Update can't break Ordering.Application.DTOs.
Position
Below the diagonal: Ordering.Application.Commands.Customers.Update uses a module listed above it, which is the healthy direction.
Ordering.Application.Commands.Customers.Update uses Ordering.Core.Repositories.Command, so a change to Ordering.Core.Repositories.Command can break Ordering.Application.Commands.Customers.Update, while a change to Ordering.Application.Commands.Customers.Update can't break Ordering.Core.Repositories.Command.
Position
Below the diagonal: Ordering.Application.Commands.Customers.Update uses a module listed above it, which is the healthy direction.
Ordering.Application.Commands.Customers.Update uses Ordering.Core.Repositories.Query, so a change to Ordering.Core.Repositories.Query can break Ordering.Application.Commands.Customers.Update, while a change to Ordering.Application.Commands.Customers.Update can't break Ordering.Core.Repositories.Query.
Position
Below the diagonal: Ordering.Application.Commands.Customers.Update uses a module listed above it, which is the healthy direction.
Ordering.Application.Handlers.CommandHandler uses Ordering.Core.Repositories.Command, so a change to Ordering.Core.Repositories.Command can break Ordering.Application.Handlers.CommandHandler, while a change to Ordering.Application.Handlers.CommandHandler can't break Ordering.Core.Repositories.Command.
Position
Below the diagonal: Ordering.Application.Handlers.CommandHandler uses a module listed above it, which is the healthy direction.
Ordering.Application.Handlers.CommandHandler uses Ordering.Core.Repositories.Query, so a change to Ordering.Core.Repositories.Query can break Ordering.Application.Handlers.CommandHandler, while a change to Ordering.Application.Handlers.CommandHandler can't break Ordering.Core.Repositories.Query.
Position
Below the diagonal: Ordering.Application.Handlers.CommandHandler uses a module listed above it, which is the healthy direction.
MTShop.API.Controllers uses MTShop.Application.Commands.Auth, so a change to MTShop.Application.Commands.Auth can break MTShop.API.Controllers, while a change to MTShop.API.Controllers can't break MTShop.Application.Commands.Auth.
Position
Below the diagonal: MTShop.API.Controllers uses a module listed above it, which is the healthy direction.
MTShop.API.Controllers uses MTShop.Application.Commands.Customer, so a change to MTShop.Application.Commands.Customer can break MTShop.API.Controllers, while a change to MTShop.API.Controllers can't break MTShop.Application.Commands.Customer.
Position
Below the diagonal: MTShop.API.Controllers uses a module listed above it, which is the healthy direction.
MTShop.API.Controllers uses MTShop.Application.Commands.Products, so a change to MTShop.Application.Commands.Products can break MTShop.API.Controllers, while a change to MTShop.API.Controllers can't break MTShop.Application.Commands.Products.
Position
Below the diagonal: MTShop.API.Controllers uses a module listed above it, which is the healthy direction.
MTShop.API.Controllers uses MTShop.Application.Commands.Tenant, so a change to MTShop.Application.Commands.Tenant can break MTShop.API.Controllers, while a change to MTShop.API.Controllers can't break MTShop.Application.Commands.Tenant.
Position
Below the diagonal: MTShop.API.Controllers uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Persistence uses MTShop.Core.Entities, so a change to MTShop.Core.Entities can break MTShop.Infrastructure.Persistence, while a change to MTShop.Infrastructure.Persistence can't break MTShop.Core.Entities.
Position
Below the diagonal: MTShop.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Persistence uses MTShop.Core.Entities.Admin, so a change to MTShop.Core.Entities.Admin can break MTShop.Infrastructure.Persistence, while a change to MTShop.Infrastructure.Persistence can't break MTShop.Core.Entities.Admin.
Position
Below the diagonal: MTShop.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Persistence uses MTShop.Application.Common.Models, so a change to MTShop.Application.Common.Models can break MTShop.Infrastructure.Persistence, while a change to MTShop.Infrastructure.Persistence can't break MTShop.Application.Common.Models.
Position
Below the diagonal: MTShop.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Persistence uses MTShop.Application.Interfaces, so a change to MTShop.Application.Interfaces can break MTShop.Infrastructure.Persistence, while a change to MTShop.Infrastructure.Persistence can't break MTShop.Application.Interfaces.
Position
Below the diagonal: MTShop.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Persistence uses MTShop.Infrastructure.Persistence.Admin, so a change to MTShop.Infrastructure.Persistence.Admin can break MTShop.Infrastructure.Persistence, while a change to MTShop.Infrastructure.Persistence can't break MTShop.Infrastructure.Persistence.Admin.
Position
Below the diagonal: MTShop.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Persistence uses MTShop.Application, so a change to MTShop.Application can break MTShop.Infrastructure.Persistence, while a change to MTShop.Infrastructure.Persistence can't break MTShop.Application.
Position
Below the diagonal: MTShop.Infrastructure.Persistence uses a module listed above it, which is the healthy direction.
Ordering.API.Controllers uses Ordering.Application.DTOs, so a change to Ordering.Application.DTOs can break Ordering.API.Controllers, while a change to Ordering.API.Controllers can't break Ordering.Application.DTOs.
Position
Below the diagonal: Ordering.API.Controllers uses a module listed above it, which is the healthy direction.
Ordering.API.Controllers uses Ordering.Core.Entities, so a change to Ordering.Core.Entities can break Ordering.API.Controllers, while a change to Ordering.API.Controllers can't break Ordering.Core.Entities.
Position
Below the diagonal: Ordering.API.Controllers uses a module listed above it, which is the healthy direction.
Ordering.API.Controllers uses Ordering.Application.Commands.Customers.Update, so a change to Ordering.Application.Commands.Customers.Update can break Ordering.API.Controllers, while a change to Ordering.API.Controllers can't break Ordering.Application.Commands.Customers.Update.
Position
Below the diagonal: Ordering.API.Controllers uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Seed uses MTShop.Core.Entities.Admin.Identity, so a change to MTShop.Core.Entities.Admin.Identity can break MTShop.Infrastructure.Seed, while a change to MTShop.Infrastructure.Seed can't break MTShop.Core.Entities.Admin.Identity.
Position
Below the diagonal: MTShop.Infrastructure.Seed uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Seed uses MTShop.Core.Entities.Identity, so a change to MTShop.Core.Entities.Identity can break MTShop.Infrastructure.Seed, while a change to MTShop.Infrastructure.Seed can't break MTShop.Core.Entities.Identity.
Position
Below the diagonal: MTShop.Infrastructure.Seed uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Seed uses MTShop.Application.Common.Models, so a change to MTShop.Application.Common.Models can break MTShop.Infrastructure.Seed, while a change to MTShop.Infrastructure.Seed can't break MTShop.Application.Common.Models.
Position
Below the diagonal: MTShop.Infrastructure.Seed uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Seed uses MTShop.Infrastructure.Persistence.Admin, so a change to MTShop.Infrastructure.Persistence.Admin can break MTShop.Infrastructure.Seed, while a change to MTShop.Infrastructure.Seed can't break MTShop.Infrastructure.Persistence.Admin.
Position
Below the diagonal: MTShop.Infrastructure.Seed uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Seed uses MTShop.Application, so a change to MTShop.Application can break MTShop.Infrastructure.Seed, while a change to MTShop.Infrastructure.Seed can't break MTShop.Application.
Position
Below the diagonal: MTShop.Infrastructure.Seed uses a module listed above it, which is the healthy direction.
MTShop.Infrastructure.Seed uses MTShop.Infrastructure.Persistence, so a change to MTShop.Infrastructure.Persistence can break MTShop.Infrastructure.Seed, while a change to MTShop.Infrastructure.Seed can't break MTShop.Infrastructure.Persistence.
Position
Below the diagonal: MTShop.Infrastructure.Seed uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 41% · Weak · gated by D18, R1, X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2025 — Security Misconfiguration
420
High / Critical
A05:2025 — Injection
303
Medium
A03:2025 — Software Supply Chain Failures
145
High / Critical
A07:2025 — Authentication Failures
46
High / Critical
Roadmap
Immediately resolve the 124 orphaned files in Knowledge Freshness, prioritizing Program.cs, REDACTED, and REDACTED, and fix the 25 leaked secrets in REDACTED Scanning, starting with REDACTED, REDACTED, and REDACTED. Expand the root README to include getting-started instructions, an architecture overview, and a project map. Record significant design decisions as individual documents in a docs/adr folder, capturing the date, context, decision, and consequences for each.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Expand the README with getting-started, architecture overview and a project map.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 — 238
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 — 1043
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 — 471
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
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. 110 of 115 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 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 — 115 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, 1726 of 1752 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.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 33 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 6 test source file(s) (.js) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: dotnet-core-nuget-github/CryptoTest/CryptoTest.csproj : error NU1101: Unable to find package Mahedee.CryptoEngine. No packages exist with this id in source(s): /usr/share/dotnet/library-packs, nuget.org [/tmp/codehealth-iso-6877fd9d61c845399ba3212….
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Maven POM, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Maven dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 186 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 'dotnet-core-nuget-github/CryptoTest/CryptoTest.csproj' with message: Unable to find package Mahedee.CryptoEngine. No packages exist with this id in source(s): /usr/share/dotnet/library-packs, nuget.org.
D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
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; `sd-docker-demo/LocationA.API/appsettings.json`, `sd-demo/Location.API/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.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. 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. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
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. `dms-azure-blob-aspnet/Controllers/DocumentsController.cs` 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.
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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — zookeeper Pulling kafka Pulling sqlserver Pulling zookeeper Error Get "https://registry-1.docker.io/v2/": Forbidden kafka Error Get "https://registry-1.docker.io/v2/": Forbidden sqlserver Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: productservice Skipped - No image to be pulled orderservice Skipped - No image to be pulled kafka Pulling sqlserver Pulling zookeeper Pulling kafka Error Get "https://registry-1.docker.io/v2/": Forbidden zookeeper Error context canceled sqlserver Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
IC1 Incompleteness & stubs — 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. 118 further occurrence(s) are not listed individually; the score already reflects all 158.
S1 Web-Security Posture — 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. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
X2 Cancellation propagation — 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. 442 further occurrence(s) are not listed individually; the score already reflects all 482.
X4 Structured logging — 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. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for dotnet-core-nuget-github/CryptoTest/CryptoTest.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
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.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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.
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").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
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.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (5): D19, D21, 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.
Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with AdminDbContextInitializer.TrySeedAsync (cognitive 28), MultitenantDbContextInitializer.TrySeedAsync (cognitive 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.0 / 10Stronggated by 6 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 4 FunctionTooLong finding(s) in God Classes — start with EditCustomer.js, AddCustomer.js, AddProduct.js. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with HrmDbContext.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TooManyMethods finding(s) in God Classes — start with QueryRepository.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
118 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 66 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (5 lines × 3) finding(s) in Code Duplication — start with UpdateRoleCommand.cs, CreateUserCommand.cs, AssignUsersRoleCommand.cs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 8 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with IdentityService.cs (7), CreateUserCommand.cs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with CustomerQueryRepository.cs (2), ServiceCollectionExtensions.cs, EditCustomerHandler.cs. — One of this dimension's main actionable groups (5 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
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 Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
39 test methods: 39 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 6 `it`/`test` case(s) across 6 test file(s) declaring at least one beside 33 .NET test method(s); its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality8.2 / 10Adequategated by 2 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 33 tests. Measured on the C# suite only — at least 6 test source file(s) (.js) went unread, so its test quality is unmeasured and is not in these counts.
No assertions (empty test): Test1 · ×2multi-env-app/src/HRM/HRM.Tests/UnitTest1.cs:5
Test project verifies nothing: HRM.Testjenkins-demo/HRM/HRM.Test/UnitTest1.cs:7
What to do
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with UnitTest1.cs (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with UnitTest1.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
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 25 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (18), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (25 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 624 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 94 direct `PackageReference`(s), and 159 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Maven POM, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
71 deducted debt markers + unmeasured dead symbols across 28396 LoC in the .NET projects (1.6/KLoC) → score 6.8. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Whole file has no live code — 6 debt markers inside it · ×2token-based-auth-core-react/ECommerce/Ordering.Application/Common/Security/TokenGenerator.cs:1
What to do
Resolve the 40 WriteOnlyPrivateField finding(s) in Explicit Debt — start with REDACTED (32), REDACTED (2), DbConnector.cs. — One of this dimension's main actionable groups (40 issue-level).
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with TemplatePack.csproj, ExportReportAPI.csproj. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 14 CommentedOutCode finding(s) in Explicit Debt — start with DependencyInjection.cs (4), CatalogContext.cs (3), WordTemplate.cs (3). — One of this dimension's main actionable groups (14 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
104 projects, 827 source files, 29146 hand-written lines of code (28396 production / 750 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 8515 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 43 inter-project edges (build failed). Measured across 51 solutions loaded as one workspace: `MultiTenant/MultiTenant.sln`, `token-based-auth-core-react/ECommerce/ECommerce.sln`, `token-based-auth-ng/ECommerce/ECommerce.sln`, `token-based-auth-core/ECommerce/ECommerce.sln`, `EventSourcing/EventSourcing.sln`, `CleanArchitectureTemplate/CleanArchitecture/CleanArchTemplate.sln`, `saga-choreography-v02/EcommerceSaga.sln`, `CleanArchitectureDemo/Ecommerce/Ecommerce.sln`, `ocelot-swagger/APIGateway/APIGateway.sln`, `service-mesh/ServiceMesh/ServiceMesh.sln`, `api-gateway-ocelot/APIGateway/APIGateway.sln`, `multi-env-app/src/HRM/HRM.sln`, `sd-demo/SDDemo.sln`, `sd-docker-demo/SDDemoDocker.sln`, `health-check/HealthCheck/HealthCheck.sln`, `saga-choreography/ECommerce/ECommerce.sln`, `MicroservicesDemo/MicroservicesDemo.slnx`, `asp-azure-key-vault/asp-azure-key-vault.sln`, `AuditLogEFPlus/EFPlusAuditLog.sln`, `AuditLogRawSQL/AuditTrail.sln`, `EFBulkBatch/EFBulkBatch.sln`, `export-report-api/ExportReport.sln`, `jenkins-demo/HRM/HRM.sln`, `api-gateway-ocelot-qos/QoS.sln`, `hrm/HRM/HRM.sln`, `DapperDemo/DapperDemo/DapperDemo.sln`, `aks-hrm/HRM.API.sln`, `kubernetes-demo/KubernetesDemo/KubernetesDemo.sln`, `react-redux-toolkit/ECommerce/ECommerce.sln`, `ConcurrencyAppToken/ConcurrencyHandling.sln`, `ConcurrencyDBToken/ConcurrencyHandling.sln`, `ConcurrencyEtags/ConcurrencyHandling.sln`, `ConcurrencyHyperMedia/ConcurrencyHandling.sln`, `ConcurrencyRawSQL/Concurrency.sln`, `IdempotentDemo/IdempotentDemo.sln`, `dms-azure-blob-aspnet/DMS.sln`, `grafana-dotnet-core/EcommerceApi/EcommerceSolution.sln`, `micro-frontend/product-backend/ProductSln.sln`, `factory-pattern/FactoryPattern.sln`, `ocp/OCP/OCP.slnx`, `dotnet-core-nuget-github/CryptoSolution.sln`, `micro-frontend/customer-backend/Customer.sln`, `PrivateRegistryDemo/PrivateRegistryDemo.sln`, `IValidatebleObject/IValidatebleObjectSln.sln`, `MiddlewareExample/MiddlewareSolution.sln`, `CacheRefreshFunction/CacheRefreshFunction.sln`, `ECommerceFacade/ECommerceFacade.sln`, `FacadePattern/FacadePattern/FacadePattern.sln`, `ObserverPattern/GenericSolution/ObserverPattern.sln`, `ObserverPattern/StockNotification/StockNotifications/StockNotifications.sln`, `singleton-pattern/SingletonDemo/SingletonDemo.sln`.
Build failed
What to do
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 project's documentation is mostly well-structured and complete for its own directories: each README of a binary-tree-traversal-app/ or factory-pattern/ subdirectory documents that directory (and the repository root has no overview, installation, or usage guidance). The XML-doc coverage figures reflect an internal codebase with only 3% coverage across the listed namespaces; this is not a defect but evidence of sparse documentation. There are no visible defects among the shown files. The project's documentation is a single root README plus scattered READMEs for directories (e.g. 'token-based-auth-ng/ECommerce/Readme.txt') and an XML-doc coverage of 18% across the repository; it is thin on overview, installation, usage, contribution guidance, and licence, with most documents clipped mid-sentence.
Improve Documentation Quality — currently 5.6/10. — The project's documentation is mostly well-structured and complete for its own directories: each README of a binary-tree-traversal-app/ or factory-pattern/ subdirectory documents that directory (and the repository root has no overview, installation, or usage guidance). The XML-doc coverage figures reflect an internal codebase with only 3% coverage across the listed namespaces; this is not a defect but evidence of sparse documentation. There are no visible defects among the shown files. The project's documentation is a single root README plus scattered READMEs for directories (e.g. 'token-based-auth-ng/ECommerce/Readme.txt') and an XML-doc coverage of 18% across the repository; it is thin on overview, installation, usage, contribution guidance, and licence, with most documents clipped mid-sentence.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 naming inconsistencies across 200 sampled symbols.
Inconsistent namespace casing for the 'ECommerce' module. Some namespaces use 'ECommerceApi' (CamelCase for the acronym) while others use 'EcommerceApi' (lowercase 'c'). Additionally, the DbContext types are named inconsistently: 'AppDbContext' vs 'EcommerceDbContext'.
✓ On the Gold path — maintain.
Detailed fixes: d21_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.
2 domain type(s) cross context boundaries across 36 contexts.
Cross-context type Customer (Ordering → DapperDemo) · ×2REDACTED:27
What to do
Resolve the 2 Cross-context type Customer (Ordering → DapperDemo) finding(s) in Boundary Type-Coupling — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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.
99 % of calls cross a namespace and 6 % go through an interface, but 99 % 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: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
20 finding(s): 0 critical, 20 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 20 REDACTED finding(s) in Secrets (history) — start with REDACTED (17), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (20 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
303 finding(s): 0 critical, 0 high, 303 medium, 0 low. semgrep hit a parse error in 1 file(s) — `dms-azure-blob-aspnet/Controllers/DocumentsController.cs` (line 25) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 291 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (65), REDACTED (34), REDACTED (34). — One of this dimension's main actionable groups (291 warning-level).
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
145 finding(s): 22 critical, 74 high, 37 medium, 12 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (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), so this is not the whole dependency surface and the result is reported at reduced confidence.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 72 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (72). — One of this dimension's main actionable groups (72 issue-level).
Resolve the 21 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 326 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (89), REDACTED (50), REDACTED (34). — One of this dimension's main actionable groups (326 warning-level).
Resolve the 26 High IaC finding(s) in IaC & Container Security — start with REDACTED (12), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 68 Low IaC finding(s) in IaC & Container Security — start with REDACTED (16), REDACTED (14), REDACTED (12). — One of this dimension's main actionable groups (68 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
125 of 125 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs. Counted over 125 of the 789 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned fileCleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs:1
What to do
Resolve the 124 Orphaned file finding(s) in Knowledge Freshness — start with Program.cs (19), REDACTED (10), REDACTED (6). — One of this dimension's main actionable groups (124 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with IQueryRepository.cs. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
0/12 workload(s) run every container under a seccomp profile; 0/12 declare an AppArmor/SELinux profile.
No seccomp profile · ×12REDACTED:2
What to do
Resolve the 12 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
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.
4 end-of-life runtime(s) and 0 end-of-life framework(s), read from 105 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 4 End-of-life runtime finding(s) in Platform End-of-Life — start with Shared.csproj, LocationC.API.csproj, EFBulkBatch.csproj. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels2.1 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×10) — token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:53, token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:58, token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:63, …
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×10) — token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:54, token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:59, token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:64, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×6) — micro-frontend/customer-frontend/public/index.html:2, micro-frontend/header-frontend/public/index.html:2, micro-frontend/master-frontend/public/index.html:2, …
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.span1` moves (`animation: anim 20s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — micro-frontend/master-frontend/src/assets/homeStyle.css:29
`.overflow` moves (`animation: animate 5s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — micro-frontend/master-frontend/src/assets/homeStyle.css:99
`.span5` moves (`animation: anim 18s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — micro-frontend/master-frontend/src/assets/homeStyle.css:148
`.span6` moves (`animation: anim 17s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — micro-frontend/master-frontend/src/assets/homeStyle.css:161
`.span7` moves (`animation: anim 10s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — micro-frontend/master-frontend/src/assets/homeStyle.css:188
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 10 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
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 — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
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.
`KafkaEventBus` is a singleton (one shared instance) but mutates instance state outside any lock (_handlers, _subscribedTopics, _isConsuming; e.g. `_handlers` at line 69). — MicroservicesDemo/src/Shared/EventBus/EventBus/KafkaEventBus.cs:8
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
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.
The namespaces Domain.Entities ↔ Domain.Events.CatalogItem depend on each other. The lightest dependency in the cycle is Domain.Entities → Domain.Events.CatalogItem (Domain.Entities.CatalogItem → Domain.Events.CatalogItem.CatalogItemCreated, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — EventSourcing/Domain/Entities/CatalogItem.cs:2
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
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.
`IIdentityService` declares 19 members: `CreateUserAsync`, `CreateUserAsync`, `GetUserNameAsync`, `GetUserIdAsync`, `GetUserAsync`, `UpdateUserAsync`, `DeleteUserAsync`, `IsInRoleAsync`, `GetUserRolesAsync`, `SignInUserAsync`, `GetUserDetailsAsync`, `AssignUserToRoleAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetRolesAsync`, `GetRoleAsync`, `CreateRoleAsync`, `UpdateRoleAsync`, `DeleteRoleAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — MultiTenant/MTShop.Application/Interfaces/IIdentityService.cs:6
`IAdminIdentityService` declares 19 members: `CreateUserAsync`, `CreateUserAsync`, `GetUserNameAsync`, `GetUserIdAsync`, `GetUserAsync`, `UpdateUserAsync`, `DeleteUserAsync`, `IsInRoleAsync`, `GetUserRolesAsync`, `SignInUserAsync`, `GetUserDetailsAsync`, `AssignUserToRoleAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetRolesAsync`, `GetRoleAsync`, `CreateRoleAsync`, `UpdateRoleAsync`, `DeleteRoleAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — MultiTenant/MTShop.Application/Interfaces/Admin/IAdminIdentityService.cs:6
`IIdentityService` declares 20 members: `CreateUserAsync`, `SigninUserAsync`, `GetUserIdAsync`, `GetUserDetailsAsync`, `GetUserDetailsByUserNameAsync`, `GetUserNameAsync`, `DeleteUserAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetAllUsersDetailsAsync`, `UpdateUserProfile`, `CreateRoleAsync`, `DeleteRoleAsync`, `GetRolesAsync`, `GetRoleByIdAsync`, `UpdateRole`, `IsInRoleAsync`, `GetUserRolesAsync`, `AssignUserToRole`, `UpdateUsersRole`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×3) — token-based-auth-core-react/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:3, token-based-auth-ng/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:9, token-based-auth-core/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:3
`IQueryRepository<TEntity>` declares 30 members under just 3 distinct name(s): `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `GetDataTableAsync`, `GetDataTableAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 30 separate responsibilities: a caller binds to 3 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 30 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs:6
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
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 Protection6.0 / 10Adequate✓ 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.
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
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 Trail10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
Other · Security — Whether GDPR data-subject requests are supported in code — erasure, export/portability, consent.
Method: Roslyn scan: GDPR data-subject-rights corroboration (erasure/export/consent vocabulary co-occurring with subject-id store crossing or explicit GDPR pattern). Deterministic, gated by PII.
Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
What to do
Implement data export/portability for a data subject (a machine-readable export of their personal data).
Track GDPR consent (lawful basis) alongside the personal data it authorises.
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 aggregate10.0 / 10Exemplary○ Nothing flagged
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.
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.
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.
`Customer.TenantId` 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. — MultiTenant/MTShop.Core/Entities/Customer.cs:13
`Product.TenantId` 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. — MultiTenant/MTShop.Core/Entities/Product.cs:12
`TenantEntity.TenantKey` 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. — MultiTenant/MTShop.Core/Entities/Admin/TenantEntity.cs:13
`UpdateCatalogItemCommand.CatalogItemId` 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. — EventSourcing/Application/Commands/CatalogItems/UpdateCatalogItemCommand.cs:23
`OrderCreatedEvent.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. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:5
`OrderCreatedEvent.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. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:6
`ProductCreatedEvent.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. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductCreatedEvent.cs:5
`ProductUpdatedEvent.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. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductUpdatedEvent.cs:5
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
DM4 · Rich vs anemic model3.8 / 10Adequate✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`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. — MultiTenant/MTShop.Core/Entities/Customer.cs:6
`Product` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — MultiTenant/MTShop.Core/Entities/Product.cs:7
`TenantEntity` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — MultiTenant/MTShop.Core/Entities/Admin/TenantEntity.cs:10
`Customer` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×5) — token-based-auth-core-react/ECommerce/Ordering.Core/Entities/Customer.cs:6, token-based-auth-ng/ECommerce/Ordering.Core/Entities/Customer.cs:6, token-based-auth-core/ECommerce/Ordering.Core/Entities/Customer.cs:6, …
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 repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.
Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.
Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.
`ICustomerCommandRepository` is a repository over `Customer`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Customer` through its owning aggregate instead. — token-based-auth-core-react/ECommerce/Ordering.Core/Repositories/Command/ICustomerCommandRepository.cs:7
`CustomerRepository` is a repository over `Customer`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Customer` through its owning aggregate instead. — DapperDemo/DapperDemo/Customer.API/Repositories/CustomerRepository.cs:12
What to do
Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
Other · Domain Modelling — Whether 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.
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.
OrderService.Models.Order's [ProductId, Status] are judged in OrderService.Controllers.OrdersController, OrderService.Services.ProductEventHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
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.
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.
`BaseDomainEvent` 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. — EventSourcing/Domain/Entities/Common/BaseDomainEvent.cs:8
`CreateCatalogItemCommand` 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. — EventSourcing/Application/Commands/CatalogItems/CreateCatalogItemCommand.cs:7
`DeleteCatalogItemCommand` 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. — EventSourcing/Application/Commands/CatalogItems/DeleteCatalogItemCommand.cs:7
`UpdateCatalogItemCommand` 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. — EventSourcing/Application/Commands/CatalogItems/UpdateCatalogItemCommand.cs:7
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.
`OrderEventHandler.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). — MicroservicesDemo/src/Services/ProductService/ProductService/Services/OrderEventHandler.cs:19
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.
`Role.RoleDeleteCommandHandler.Handle` mutates persistent state (a repository write one hop away, in IdentityService.DeleteRoleAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — MultiTenant/MTShop.Application/Commands/Role/RoleDeleteCommand.cs:19
`CatalogItems.CreateCatalogItemCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — EventSourcing/Application/Commands/CatalogItems/CreateCatalogItemCommand.cs:55
`Services.ProductEventHandler.Handle` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — MicroservicesDemo/src/Services/OrderService/OrderService/Services/ProductEventHandler.cs:19
What to do
Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
Other · Event Sourcing — Whether Apply/When folds reconstruct state purely from the event (no DateTime.Now, Guid.NewGuid, Random or IO) so replay is reproducible.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether persisted events are immutable facts (init-only/readonly) — a settable event member lets stored history be rewritten.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
This persisted event exposes settable member(s) (OrderId, ProductId, Quantity, TotalPrice, CustomerEmail) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:3
This persisted event exposes settable member(s) (ProductId, Name, Price, Stock) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductCreatedEvent.cs:3
This persisted event exposes settable member(s) (ProductId, Name, Description, Price, Stock, PreviousPrice, PreviousStock) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductUpdatedEvent.cs:3
What to do
Make every event type immutable: records with init-only properties, or classes with readonly fields set only in the constructor.
Do you agree with this assessment?
ES3 · PII in the event store5.6 / 10Adequate✓ Tool-verified
Other · Event Sourcing — Whether the append-only event log avoids un-erasable personal data (or has a crypto-shredding strategy) — a GDPR right-to-erasure risk.
Method: Roslyn (event-sourcing gated): high-confidence PII flagged Warning; ambiguous name-like fields adjudicated by language model as person versus fictional. Advisory without model, definitive with.
Persisted event carries personal data (CustomerEmail) — no crypto-shredding strategy covers it, so it collides with the GDPR right-to-erasure. — MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:3
What to do
Adopt crypto-shredding (store PII encrypted with a per-subject key you can throw away) or keep PII out of events and reference it by id so erasure stays possible.
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.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×13) — MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:42, MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:54, token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
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.
`Login` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Archive/ECommerce/Controllers/AuthController.cs:19
`Index` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:18
`GetProducts` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:95, ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:94
`AddRepositories` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/DependencyInjection.cs:46
`SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×8) — CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:210, CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:219, CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:241, …
`GetByName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:42
`GetConnectionString` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:54
`SetTenant` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — MultiTenant/MTShop.Infrastructure/Implementations/TenantService.cs:49
`AddApplication` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×3) — token-based-auth-core-react/ECommerce/Ordering.Application/DependencyInjection.cs:13, token-based-auth-core/ECommerce/Ordering.Application/DependencyInjection.cs:13, token-based-auth-ng/ECommerce/Ordering.Application/DependencyInjection.cs:13
`GetAllUsersDetailsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122, token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122, token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×17) — REDACTED:39, AuditLogEFPlus/AuditLog.API/Program.cs:42, REDACTED:105, …
A placeholder e-mail address ("customer@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. — ECommerceFacade/ECommerceFacade/Program.cs:98
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.
The root README is 2 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 102 of 104 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the 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.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
Only 21/104 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
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.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Strong✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
What to do
Make types internal by default and expose only the deliberate public API — even for a small library, every public type is a stability contract.
Do you agree with this assessment?
P2 · Observability6.6 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 44/84 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 84, 69 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.
Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — CacheRefreshFunction/CacheRefreshAzureFunction/CacheRefreshTimerTriggerFunction.cs:14
What to do
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
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. (×8) — saga-choreography-v02/Order.API/Program.cs:74, saga-choreography-v02/Catalog.API/Program.cs:84, saga-choreography-v02/Payment.API/Program.cs:67, …
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.
No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.
What to do
On hot paths, prefer Span<T>/ReadOnlySpan<T>, ArrayPool<T>, stackalloc and ValueTask to cut the allocations those paths would otherwise make.
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.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 101 plain JS — the untyped files are micro-frontend/customer-frontend/config-overrides.js, micro-frontend/customer-frontend/src/App.js, micro-frontend/customer-frontend/src/App.test.js, micro-frontend/customer-frontend/src/components/CustomerComponent/CustomersListComponent.js, micro-frontend/customer-frontend/src/components/CustomerComponent/DataTableComponent.js, micro-frontend/customer-frontend/src/index.js (+95 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
micro-frontend/customer-frontend/ and micro-frontend/product-frontend/ are near-verbatim copies of each other: 14 files are byte-identical under the same relative paths (~233 lines; the trees hold 23 and 26 files). That is one structural fact, not 14 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — micro-frontend/customer-frontend/README.md:1
micro-frontend/customer-frontend/ and micro-frontend/header-frontend/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~226 lines; the trees hold 23 and 18 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — micro-frontend/customer-frontend/README.md:1
micro-frontend/header-frontend/ and micro-frontend/product-frontend/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~226 lines; the trees hold 18 and 26 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — micro-frontend/header-frontend/README.md:1
micro-frontend/header-frontend/ and react-redux-toolkit/redux-app/ are near-verbatim copies of each other: 10 files are byte-identical under the same relative paths (~204 lines; the trees hold 18 and 32 files). That is one structural fact, not 10 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — micro-frontend/header-frontend/README.md:1
12 duplicated blocks under token-based-auth-core-react/ecommerce.client/src/components/ have copies in at least two of the sibling directories Auth, Customer, Role, User, UsersRoles — 8 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:29
8 duplicated blocks under micro-frontend/ have copies in at least two of the sibling directories customer-frontend, header-frontend, product-frontend — 4 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — micro-frontend/customer-frontend/config-overrides.js:2
react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:9 · react-redux-toolkit/redux-app/src/components/product/EditProduct.js:9 — the two spans are one implementation copied and then locally edited — 465 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:9
react-redux-toolkit/redux-app/src/components/customer/CustomerList.js:19 · react-redux-toolkit/redux-app/src/components/product/ProductsList.js:14 — the two spans are one implementation copied and then locally edited — 304 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — react-redux-toolkit/redux-app/src/components/customer/CustomerList.js:19
react-redux-toolkit/redux-app/src/redux/slices/customersSlice.js:10 · react-redux-toolkit/redux-app/src/redux/slices/productsSlice.js:10 — the two spans are one implementation copied and then locally edited — 303 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — react-redux-toolkit/redux-app/src/redux/slices/customersSlice.js:10
token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:29 · token-based-auth-core-react/ecommerce.client/src/components/User/DeleteUser.js:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:29
token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:4 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:4 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:4
token-based-auth-core-react/ecommerce.client/src/components/Role/EditRole.js:28 · token-based-auth-core-react/ecommerce.client/src/components/User/UpdateUser.js:43 — the two spans are one implementation copied and then locally edited — 180 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — token-based-auth-core-react/ecommerce.client/src/components/Role/EditRole.js:28
token-based-auth-core-react/ecommerce.client/src/components/Role/Roles.js:14 · token-based-auth-core-react/ecommerce.client/src/components/User/Users.js:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Role/Roles.js:14
react-redux-toolkit/redux-app/src/components/customer/AddCustomer.js:64 · react-redux-toolkit/redux-app/src/components/customer/AddCustomer.js:101 · react-redux-toolkit/redux-app/src/components/product/AddProduct.js:87 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — react-redux-toolkit/redux-app/src/components/customer/AddCustomer.js:64
react-redux-toolkit/redux-app/src/components/product/AddProduct.js:43 · react-redux-toolkit/redux-app/src/components/product/EditProduct.js:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — react-redux-toolkit/redux-app/src/components/product/AddProduct.js:43
REDACTED:6 · REDACTED:76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:6
REDACTED:53 · REDACTED:100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:53
token-based-auth-core-react/ecommerce.client/src/components/User/DeleteUser.js:18 · token-based-auth-core-react/ecommerce.client/src/components/User/UpdateUser.js:28 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/User/DeleteUser.js:18
react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:74 · react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:74
micro-frontend/product-frontend/src/components/CategoryComponent/CategoryListComponent.js:5 · micro-frontend/product-frontend/src/components/ProductComponent/ProductListComponent.js:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — micro-frontend/product-frontend/src/components/CategoryComponent/CategoryListComponent.js:5
react-redux-toolkit/redux-app/src/services/CustomerService.js:4 · react-redux-toolkit/redux-app/src/services/ProductService.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — react-redux-toolkit/redux-app/src/services/CustomerService.js:4
micro-frontend/customer-frontend/config-overrides.js:2 · micro-frontend/header-frontend/config-overrides.js:2 · micro-frontend/product-frontend/config-overrides.js:2 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — micro-frontend/customer-frontend/config-overrides.js:2
micro-frontend/customer-frontend/src/components/CustomerComponent/DataTableComponent.js:46 · micro-frontend/product-frontend/src/components/ProductComponent/DataTableComponent.js:56 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — micro-frontend/customer-frontend/src/components/CustomerComponent/DataTableComponent.js:46
token-based-auth-core-react/ecommerce.client/src/components/Role/CreateRole.js:32 · token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:59 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Role/CreateRole.js:32
react-redux-toolkit/redux-app/src/components/product/EditProduct.js:68 · react-redux-toolkit/redux-app/src/components/product/EditProduct.js:91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — react-redux-toolkit/redux-app/src/components/product/EditProduct.js:68
token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:41 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:103 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:41
micro-frontend/customer-frontend/src/reportWebVitals.js:1 · micro-frontend/header-frontend/src/reportWebVitals.js:1 · micro-frontend/master-frontend/src/reportWebVitals.js:1 · micro-frontend/product-frontend/src/reportWebVitals.js:1 · +2 more site(s) not listed — the 6 copies are spread across 6 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — micro-frontend/customer-frontend/src/reportWebVitals.js:1
micro-frontend/header-frontend/src/index.js:19 · micro-frontend/product-frontend/src/index.js:20 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — micro-frontend/header-frontend/src/index.js:19
token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:22 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:27 · token-based-auth-core-react/ecommerce.client/src/components/UsersRoles/UsersRoles.js:58 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:22
token-based-auth-core-react/ecommerce.client/src/components/Auth/Login.js:19 · token-based-auth-core-react/ecommerce.client/src/components/User/UpdateUser.js:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Auth/Login.js:19
token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:71 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:71
micro-frontend/customer-frontend/src/index.js:8 · micro-frontend/header-frontend/src/index.js:8 · micro-frontend/product-frontend/src/index.js:8 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — micro-frontend/customer-frontend/src/index.js:8
micro-frontend/master-frontend/src/App.js:18 · react-redux-toolkit/redux-app/src/App.js:17 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — micro-frontend/master-frontend/src/App.js:18
token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:72 · token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:72
token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:16 · token-based-auth-core-react/ecommerce.client/src/components/Role/EditRole.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:16
token-based-auth-core-react/ecommerce.client/src/components/Customer/Customers.jsx:2 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:2 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:2 · token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:2 — the 4 copies are spread across 4 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — token-based-auth-core-react/ecommerce.client/src/components/Customer/Customers.jsx:2
token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:115 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:124 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:134 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:115
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R4 · Test Coverage7.8 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×20) — micro-frontend/product-frontend/src/index.js:1, micro-frontend/customer-frontend/src/index.js:1, micro-frontend/header-frontend/src/index.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 19 application, 6 tooling and 12 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (19 application, 6 tooling, 12 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — token-based-auth-core-react/ecommerce.client/src/reportWebVitals.js
Nothing imports this binding — it is safe to review for removal. (×3) — react-redux-toolkit/redux-app/src/helper/ToastifyMessage.js:17, react-redux-toolkit/redux-app/src/helper/ToastifyMessage.js:24, react-redux-toolkit/redux-app/src/utils/Conversion.js:1
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. — token-based-auth-core-react/ecommerce.client/src/App.js:2
Declared in micro-frontend/customer-frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Only test files import it (first: micro-frontend/customer-frontend/src/App.test.js:1) — move it to devDependencies. — micro-frontend/customer-frontend/package.json:12
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
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.
`key` is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — Archive/ECommerce/Program.cs:14
`RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — MultiTenant/MTShop.API/Program.cs:53
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. (×37) — Archive/ECommerce/Program.cs:7, AuditLogEFPlus/AuditLog.API/Program.cs:10, AuditLogRawSQL/AuditLog.API/Program.cs:10, …
What to do
Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
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.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — MultiTenant/MTShop.Infrastructure/Implementations/TenantService.cs:49
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×3) — saga-choreography-v02/Payment.API/Services/InventoryReservedListener.cs:90, AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:132, AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:170
`Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method. — REDACTED:28
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.
`_adminDbContext` is never created by `ManageTenantRepository` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 76). Its declared type `AdminDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:76
`_multitenantDbContext` is never created by `UnitOfWork` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 91). Its declared type `MultitenantDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — MultiTenant/MTShop.Infrastructure/Persistence/UnitOfWork.cs:91
`dt` is a `DataTable`, which implements `IDisposable`, and it is created here (line 32). Every use of it in `GetChangeLogDynamic` 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 dt = …;`), which releases it at the end of the scope on every path including a throw. — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ReportingRepository.cs:32
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 103/574 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 — this work can't be stopped early once started. (×38) — REDACTED:24, REDACTED:37, MultiTenant/MTShop.API/Controllers/CustomerController.cs:24, …
No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. — MultiTenant/MTShop.API/Middlewares/ExceptionHandlingMiddleware.cs:31
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.
The guard on line 73 rejects `events` and line 74 reports that rejection as `ArgumentNullException` — but the condition's own test `!events.Any()` is true of a value that is NOT null: it is satisfied by an EMPTY `events`, and on that path `events` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — EventSourcing/Domain/Entities/Common/BaseAggregateRoot.cs:74
What to do
Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
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.
`LogDebug` at line 112 is called with an argument built by `string.Join(", ", _subscribedTopics)` (line 112), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — MicroservicesDemo/src/Shared/EventBus/EventBus/KafkaEventBus.cs:112
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.
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.
`throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. (×15) — MultiTenant/MTShop.Infrastructure/Persistence/AdminUnitOfWork.cs:48, AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:94, AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:179, …
What to do
Rethrow loses stack trace (`throw ex;`)
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.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×40) — MultiTenant/MTShop.API/Middlewares/ExceptionHandlingMiddleware.cs:63, REDACTED:59, saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:38, …
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.
This method contradicts itself about `exception`: line 52 assigns it with `as ValidationException`, which hands back null rather than throwing when the value is not a `ValidationException`, but line 54 then dereferences it directly as `exception.Errors` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `exception` once before the first use and handle the null case, or cast with `(ValidationException)` so the failure is reported where it happens — rather than leaving the two readings side by side. — CleanArchitectureTemplate/CleanArchitecture/CleanArch.API/Filters/ApiExceptionFilterAttribute.cs:54
This method contradicts itself about `exception`: line 78 assigns it with `as NotFoundException`, which hands back null rather than throwing when the value is not a `NotFoundException`, but line 84 then dereferences it directly as `exception.Message` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `exception` once before the first use and handle the null case, or cast with `(NotFoundException)` so the failure is reported where it happens — rather than leaving the two readings side by side. — CleanArchitectureTemplate/CleanArchitecture/CleanArch.API/Filters/ApiExceptionFilterAttribute.cs:84
This method contradicts itself about `cmd`: line 32 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 34 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:34
This method contradicts itself about `cmd`: line 115 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 117 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:117
This method contradicts itself about `cmd`: line 196 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 198 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:198
This method contradicts itself about `cmd`: line 25 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 27 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:27
This method contradicts itself about `cmd`: line 68 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 69 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:69
This method contradicts itself about `cmd`: line 103 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 104 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:104
This method contradicts itself about `cmd`: line 138 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 140 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:140
This method contradicts itself about `cmd`: line 176 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 178 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. (×2) — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:178, ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:178
This method contradicts itself about `cmd`: line 24 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 25 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ReportingRepository.cs:25
This method contradicts itself about `expandoObject`: line 37 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 40 then dereferences it directly as `expandoObject.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `expandoObject` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ReportingRepository.cs:40
This method contradicts itself about `cmd`: line 22 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 24 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:24
This method contradicts itself about `cmd`: line 66 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 67 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:67
This method contradicts itself about `cmd`: line 102 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 103 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:103
This method contradicts itself about `cmd`: line 137 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 139 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side. — ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:139
This method contradicts itself about `product`: line 202 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 221 then dereferences `product` as `product.Name` AFTER the block has closed, where the guard no longer applies. A null `product` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `product` truly cannot be null by then, the guard above is misleading and should go. — grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:221
92/100 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Where a method null-tests a symbol and then uses it after the guarded block closes, move the trailing work inside the block — the guard skips its body on null, it does not stop the method.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
Not included — 30 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 image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — zookeeper Pulling kafka Pulling sqlserver Pulling zookeeper Error Get "https://registry-1.docker.io/v2/": Forbidden kafka Error Get "https://registry-1.docker.io/v2/": Forbidden sqlserver Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: productservice Skipped - No image to be pulled orderservice Skipped - No image to be pulled kafka Pulling sqlserver Pulling zookeeper Pulling kafka Error Get "https://registry-1.docker.io/v2/": Forbidden zookeeper Error context canceled sqlserver Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
P1 CI/CD gates — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. Automated CI/CD gates are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
P12 CI test-gate honesty — no CI workflow found
P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
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
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
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.
WriteOnlyPrivateField Archive/ECommerce/Controllers/WeatherForecastController.cs:17— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField REDACTED:14— private ILogger<WeatherForecastController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
AC2 · Forms & labels· <label> that labels no control · ×10
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:53— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:58— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:63— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:68— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:73— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:117— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:122— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:127— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:132— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:137— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· <input> without a programmatic label · ×10
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:54— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:59— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:64— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:69— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:74— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:118— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:123— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:128— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:133— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:138— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
Mutable event: OrderCreatedEvent MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:3— This persisted event exposes settable member(s) (OrderId, ProductId, Quantity, TotalPrice, CustomerEmail) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: ProductCreatedEvent MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductCreatedEvent.cs:3— This persisted event exposes settable member(s) (ProductId, Name, Price, Stock) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
Mutable event: ProductUpdatedEvent MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductUpdatedEvent.cs:3— This persisted event exposes settable member(s) (ProductId, Name, Description, Price, Stock, PreviousPrice, PreviousStock) — an event is an immutable historical fact. A public setter lets stored history be rewritten after the fact. Use `{ get; init; }` (records) or readonly fields.
D10 · Test Quality· No assertions (empty test) · ×2
No assertions (empty test): Test1 multi-env-app/src/HRM/HRM.Tests/UnitTest1.cs:5— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): Test1 jenkins-demo/HRM/HRM.Test/UnitTest1.cs:7— Test method has an empty body — it asserts nothing and exercises no code.
NoWarnInCsproj CleanArchitectureTemplate/TemplatePack.csproj:27— NU5128 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
NoWarnInCsproj export-report-api/ExportReportAPI/ExportReportAPI.csproj:8— 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
D30 · Dependency Vulnerabilities· High vulnerability · ×2
Namespace dependency cycle EventSourcing/Domain/Entities/CatalogItem.cs:2— The namespaces Domain.Entities ↔ Domain.Events.CatalogItem depend on each other. The lightest dependency in the cycle is Domain.Entities → Domain.Events.CatalogItem (Domain.Entities.CatalogItem → Domain.Events.CatalogItem.CatalogItemCreated, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Dual write (no outbox): OrderEventHandler.Handle MicroservicesDemo/src/Services/ProductService/ProductService/Services/OrderEventHandler.cs:19— `OrderEventHandler.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).
Unlisted import 'react-router' token-based-auth-core-react/ecommerce.client/src/App.js:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
S1 · Web-Security Posture· Cryptographic key material is a compile-time constant · ×1
Cryptographic key material is a compile-time constant Archive/ECommerce/Program.cs:14— `key` is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
X2 · Cancellation propagation· Async method without CancellationToken · ×39
Async method without CancellationToken: SignInAdmin REDACTED:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignIn REDACTED:37— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync MultiTenant/MTShop.API/Controllers/CustomerController.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync MultiTenant/MTShop.API/Controllers/CustomerController.cs:31— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync MultiTenant/MTShop.API/Controllers/CustomerController.cs:38— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync MultiTenant/MTShop.API/Controllers/ProductsController.cs:22— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync MultiTenant/MTShop.API/Controllers/ProductsController.cs:28— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync MultiTenant/MTShop.API/Controllers/ProductsController.cs:34— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync MultiTenant/MTShop.API/Controllers/RoleController.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync MultiTenant/MTShop.API/Controllers/RoleController.cs:31— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync MultiTenant/MTShop.API/Controllers/RoleController.cs:38— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync MultiTenant/MTShop.API/Controllers/RoleController.cs:45— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync MultiTenant/MTShop.API/Controllers/RoleController.cs:52— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync MultiTenant/MTShop.API/Controllers/TenantController.cs:26— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync MultiTenant/MTShop.API/Controllers/TenantController.cs:33— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetByIdAsync MultiTenant/MTShop.API/Controllers/TenantController.cs:39— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync MultiTenant/MTShop.API/Controllers/TenantController.cs:46— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync MultiTenant/MTShop.API/Controllers/TenantController.cs:52— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync MultiTenant/MTShop.API/Controllers/UserController.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync MultiTenant/MTShop.API/Controllers/UserController.cs:31— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync MultiTenant/MTShop.API/Controllers/UserController.cs:38— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleExceptionAsync MultiTenant/MTShop.API/Middlewares/ExceptionHandlingMiddleware.cs:31— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: ConfigureAndMigrateAdminDB MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:24— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConfigureAndMigrateTenantDatabase MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:76— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:17— No CancellationToken parameter — this work can't be stopped early once started.
+ 14 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×37
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 12 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×20
No test reaches this file micro-frontend/product-frontend/src/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/customer-frontend/src/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/header-frontend/src/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file react-redux-toolkit/redux-app/src/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/master-frontend/src/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file react-redux-toolkit/redux-app/src/redux/store.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/customer-frontend/config-overrides.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/header-frontend/config-overrides.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/product-frontend/config-overrides.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file token-based-auth-core-react/ecommerce.client/src/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/customer-frontend/src/reportWebVitals.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/header-frontend/src/reportWebVitals.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/master-frontend/src/reportWebVitals.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/product-frontend/src/reportWebVitals.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file react-redux-toolkit/redux-app/src/reportWebVitals.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file token-based-auth-core-react/ecommerce.client/src/reportWebVitals.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/customer-frontend/src/setupProxy.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/header-frontend/src/setupProxy.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file micro-frontend/product-frontend/src/setupProxy.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file token-based-auth-core-react/ecommerce.client/public/assets/config.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×17
Symbol treated as nullable, then dereferenced unguarded CleanArchitectureTemplate/CleanArchitecture/CleanArch.API/Filters/ApiExceptionFilterAttribute.cs:54— This method contradicts itself about `exception`: line 52 assigns it with `as ValidationException`, which hands back null rather than throwing when the value is not a `ValidationException`, but line 54 then dereferences it directly as `exception.Errors` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `exception` once before the first use and handle the null case, or cast with `(ValidationException)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded CleanArchitectureTemplate/CleanArchitecture/CleanArch.API/Filters/ApiExceptionFilterAttribute.cs:84— This method contradicts itself about `exception`: line 78 assigns it with `as NotFoundException`, which hands back null rather than throwing when the value is not a `NotFoundException`, but line 84 then dereferences it directly as `exception.Message` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `exception` once before the first use and handle the null case, or cast with `(NotFoundException)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:34— This method contradicts itself about `cmd`: line 32 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 34 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:117— This method contradicts itself about `cmd`: line 115 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 117 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:198— This method contradicts itself about `cmd`: line 196 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 198 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:27— This method contradicts itself about `cmd`: line 25 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 27 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:69— This method contradicts itself about `cmd`: line 68 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 69 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:104— This method contradicts itself about `cmd`: line 103 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 104 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:140— This method contradicts itself about `cmd`: line 138 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 140 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:178— This method contradicts itself about `cmd`: line 176 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 178 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ReportingRepository.cs:25— This method contradicts itself about `cmd`: line 24 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 25 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ReportingRepository.cs:40— This method contradicts itself about `expandoObject`: line 37 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 40 then dereferences it directly as `expandoObject.Add` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `expandoObject` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:24— This method contradicts itself about `cmd`: line 22 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 24 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:67— This method contradicts itself about `cmd`: line 66 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 67 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:103— This method contradicts itself about `cmd`: line 102 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 103 then dereferences it directly as `cmd.CommandText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:139— This method contradicts itself about `cmd`: line 137 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 139 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:178— This method contradicts itself about `cmd`: line 176 assigns it with `as SqlCommand`, which hands back null rather than throwing when the value is not a `SqlCommand`, but line 178 then dereferences it directly as `cmd.Transaction` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cmd` once before the first use and handle the null case, or cast with `(SqlCommand)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Rethrow loses stack trace (`throw ex;`) MultiTenant/MTShop.Infrastructure/Persistence/AdminUnitOfWork.cs:48— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:94— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:179— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:261— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:51— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:82— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:120— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:159— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:194— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ReportingRepository.cs:48— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:49— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:81— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:120— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:161— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Rethrow loses stack trace (`throw ex;`) ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:192— `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
Unfinished stub — throws NotImplementedException MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:42— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:54— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:210— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:219— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:241— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:252— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:263— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:275— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:287— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:300— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:210— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:219— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:241— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:252— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:263— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:275— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:287— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:300— `SingleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:42— `GetByName` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:54— `GetConnectionString` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122— `GetAllUsersDetailsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122— `GetAllUsersDetailsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:122— `GetAllUsersDetailsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Duplicated block (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Role/Update/UpdateRoleCommand.cs:25— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Role/Update/UpdateRoleCommand.cs:25-29 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Role/Update/UpdateRoleCommand.cs:25-29 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Role/Update/UpdateRoleCommand.cs:25-29 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Role/Update/UpdateRoleCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Role/Update/UpdateRoleCommand.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 (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:23— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:23-27 | token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:23-27 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:23-27 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/AssignUsersRoleCommand.cs:25— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/AssignUsersRoleCommand.cs:25-29 | token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Update/AssignUsersRoleCommand.cs:25-29 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/User/Update/AssignUsersRoleCommand.cs:25-29 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/AssignUsersRoleCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Update/AssignUsersRoleCommand.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 (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/EditUserProfileCommand.cs:22— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/EditUserProfileCommand.cs:22-26 | token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Update/EditUserProfileCommand.cs:22-26 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/User/Update/EditUserProfileCommand.cs:27-31 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/EditUserProfileCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Update/EditUserProfileCommand.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 (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/UpdateUserRolesCommand.cs:20— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/UpdateUserRolesCommand.cs:20-24 | token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Update/UpdateUserRolesCommand.cs:20-24 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/User/Update/UpdateUserRolesCommand.cs:25-29 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Update/UpdateUserRolesCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Update/UpdateUserRolesCommand.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 (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Role/GetRoleQuery.cs:20— token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Role/GetRoleQuery.cs:20-24 | token-based-auth-core/ECommerce/Ordering.Application/Queries/Role/GetRoleQuery.cs:20-24 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/Role/GetRoleQuery.cs:20-24 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Role/GetRoleQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/Role/GetRoleQuery.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 (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserDetailsByUserNameQuery.cs:20— token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserDetailsByUserNameQuery.cs:20-24 | token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetUserDetailsByUserNameQuery.cs:20-24 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/User/GetUserDetailsByUserNameQuery.cs:25-29 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserDetailsByUserNameQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetUserDetailsByUserNameQuery.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 (5 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserDetailsQuery.cs:20— token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserDetailsQuery.cs:20-24 | token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetUserDetailsQuery.cs:20-24 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/User/GetUserDetailsQuery.cs:25-29 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserDetailsQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetUserDetailsQuery.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 (5 lines × 3) REDACTED:82— REDACTED:82-86 | REDACTED:82-86 | REDACTED:77-81 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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 (5 lines × 3) REDACTED:82— REDACTED:82-86 | REDACTED:82-86 | REDACTED:77-81 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:6— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:6-13 | token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:6-13 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs:6-13 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/User/Create/CreateUserCommand.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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:134— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:134-141 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:134-141 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:134-141 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:145— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:145-152 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:145-152 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:145-152 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:156— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:156-163 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:156-163 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:156-163 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:167— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:167-174 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:167-174 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:167-174 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:178— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:178-185 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:178-185 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:178-185 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:189— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:189-196 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:189-196 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:189-196 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:200— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:200-207 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:200-207 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:200-207 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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.
Anemic entity: Customer MultiTenant/MTShop.Core/Entities/Customer.cs:6— `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: Product MultiTenant/MTShop.Core/Entities/Product.cs:7— `Product` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: TenantEntity MultiTenant/MTShop.Core/Entities/Admin/TenantEntity.cs:10— `TenantEntity` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Customer token-based-auth-core-react/ECommerce/Ordering.Core/Entities/Customer.cs:6— `Customer` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Customer token-based-auth-ng/ECommerce/Ordering.Core/Entities/Customer.cs:6— `Customer` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Customer token-based-auth-core/ECommerce/Ordering.Core/Entities/Customer.cs:6— `Customer` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Customer CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Core/Entities/Customer.cs:6— `Customer` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Customer DapperDemo/DapperDemo/Customer.API/Entities/Customer.cs:5— `Customer` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
P8 · Schema migrations· Schema created with EnsureCreated() outside the migrations · ×8
Schema created with EnsureCreated() outside the migrations saga-choreography-v02/Order.API/Program.cs:74— 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 saga-choreography-v02/Catalog.API/Program.cs:84— 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 saga-choreography-v02/Payment.API/Program.cs:67— 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 multi-env-app/src/HRM/HRM.API/Program.cs:66— 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 asp-azure-key-vault/src/ECommerceApi/Program.cs:108— 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 MicroservicesDemo/src/Services/OrderService/OrderService/Program.cs:69— 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 MicroservicesDemo/src/Services/ProductService/ProductService/Program.cs:68— 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 grafana-dotnet-core/EcommerceApi/Program.cs:60— 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.
AC3 · Page structure· Page without a main landmark · ×6
Page without a main landmark micro-frontend/customer-frontend/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark micro-frontend/header-frontend/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark micro-frontend/master-frontend/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark micro-frontend/product-frontend/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark react-redux-toolkit/redux-app/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark token-based-auth-core-react/ecommerce.client/public/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×5
Animation without a prefers-reduced-motion guard micro-frontend/master-frontend/src/assets/homeStyle.css:29— `.span1` moves (`animation: anim 20s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard micro-frontend/master-frontend/src/assets/homeStyle.css:99— `.overflow` moves (`animation: animate 5s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard micro-frontend/master-frontend/src/assets/homeStyle.css:148— `.span5` moves (`animation: anim 18s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard micro-frontend/master-frontend/src/assets/homeStyle.css:161— `.span6` moves (`animation: anim 17s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard micro-frontend/master-frontend/src/assets/homeStyle.css:188— `.span7` moves (`animation: anim 10s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (4 members, 50+ identical tokens) MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:26— MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:26-70 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:24-62 | token-based-auth-core/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:24-62 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:24-62 — 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) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/EditCustomerHandler.cs:25— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/EditCustomerHandler.cs:25-46 | token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:32-53 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:32-53 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:32-53 — 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) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:41— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:41-57 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:41-57 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:41-57 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:41-57 — 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) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:60— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:60-76 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:60-76 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:60-76 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:60-76 — 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) grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:26— grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:26-67 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:72-117 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:122-187 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:274-326 — 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 (7 lines × 2) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:134— AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:134-140 | AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:172-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:134` 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) MultiTenant/MTShop.Application/DTOs/TenantDTO.cs:5— MultiTenant/MTShop.Application/DTOs/TenantDTO.cs:5-11 | MultiTenant/MTShop.Core/Entities/Admin/TenantEntity.cs:12-18 — 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) export-report-api/ExportReportAPI/Generator/Templates/ExcelTemplate.cs:77— export-report-api/ExportReportAPI/Generator/Templates/ExcelTemplate.cs:77-83 | export-report-api/ExportReportAPI/Generator/Templates/ExcelTemplate.cs:84-90 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) hrm/HRM/HRM.API/Repository/IEmployeeRepository.cs:5— hrm/HRM/HRM.API/Repository/IEmployeeRepository.cs:5-11 | jenkins-demo/HRM/HRM.API/Repository/IEmployeeRepository.cs:5-11 — before extracting anything, compare `hrm/HRM/HRM.API/Repository/IEmployeeRepository.cs` and `jenkins-demo/HRM/HRM.API/Repository/IEmployeeRepository.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 `hrm/HRM/HRM.API/Repository/IEmployeeRepository.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) hrm/HRM/HRM.API/Services/IEmployeeService.cs:5— hrm/HRM/HRM.API/Services/IEmployeeService.cs:5-11 | jenkins-demo/HRM/HRM.API/Services/IEmployeeService.cs:5-11 — before extracting anything, compare `hrm/HRM/HRM.API/Services/IEmployeeService.cs` and `jenkins-demo/HRM/HRM.API/Services/IEmployeeService.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 `hrm/HRM/HRM.API/Services/IEmployeeService.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 (11 lines × 2) REDACTED:21— REDACTED:21-31 | REDACTED:21-31 — before extracting anything, compare `REDACTED` and `REDACTED` 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 (11 lines × 2) REDACTED:21— REDACTED:21-31 | REDACTED:21-31 — before extracting anything, compare `REDACTED` and `REDACTED` 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 (11 lines × 2) REDACTED:91— REDACTED:91-101 | REDACTED:146-156 — 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 (11 lines × 2) hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:71— hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:71-81 | jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs:71-81 — before extracting anything, compare `hrm/HRM/HRM.API/Repository/EmployeeRepository.cs` and `jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs` as WHOLE FILES: this scan already matched 5 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 (11 lines × 2) hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:85— hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:85-95 | jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs:85-95 — before extracting anything, compare `hrm/HRM/HRM.API/Repository/EmployeeRepository.cs` and `jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs` as WHOLE FILES: this scan already matched 5 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.
Fake-async — async method never awaits Archive/ECommerce/Controllers/AuthController.cs:19— `Login` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits REDACTED:18— `Index` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:95— `GetProducts` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:94— `GetProducts` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits MultiTenant/MTShop.Infrastructure/Implementations/TenantService.cs:49— `SetTenant` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
FunctionTooLong: EditCustomer.EditCustomer react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:9— FunctionTooLong — EditCustomer runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AddCustomer.AddCustomer react-redux-toolkit/redux-app/src/components/customer/AddCustomer.js:7— FunctionTooLong — AddCustomer runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: AddProduct.AddProduct react-redux-toolkit/redux-app/src/components/product/AddProduct.js:7— FunctionTooLong — AddProduct runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: EditProduct.EditProduct react-redux-toolkit/redux-app/src/components/product/EditProduct.js:9— FunctionTooLong — EditProduct runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (7 lines × 3) grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:47— grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:47-53 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:97-103 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:167-173 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) MultiTenant/MTShop.Application/Common/Models/TenantsSeed.cs:10— MultiTenant/MTShop.Application/Common/Models/TenantsSeed.cs:10-16 | MultiTenant/MTShop.Application/DTOs/TenantDTO.cs:5-11 | MultiTenant/MTShop.Core/Entities/Admin/TenantEntity.cs:12-18 — 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.
Duplicated block (7 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:224— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:224-230 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:224-230 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:224-230 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 (7 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:252— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:252-258 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:252-258 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:252-258 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:25— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:25-33 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:25-33 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:25-33 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:240— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:240-248 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:240-248 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:240-248 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 × 3) REDACTED:36— REDACTED:36-44 | REDACTED:36-44 | REDACTED:31-39 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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 × 3) REDACTED:36— REDACTED:36-44 | REDACTED:36-44 | REDACTED:31-39 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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.
End-of-life runtime: .NET net5.0 saga-choreography/ECommerce/Shared/Shared.csproj:4— saga-choreography/ECommerce/Shared/Shared.csproj declares .NET net5.0 as this project's target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 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.
End-of-life runtime: .NET net6.0 sd-docker-demo/LocationC.API/LocationC.API.csproj:4— sd-docker-demo/LocationC.API/LocationC.API.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-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.
End-of-life runtime: .NET net7.0 EFBulkBatch/EFBulkBatch/EFBulkBatch.csproj:4— EFBulkBatch/EFBulkBatch/EFBulkBatch.csproj declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 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.
End-of-life runtime: .NET net9.0 multi-env-app/src/HRM/HRM.Tests/HRM.Tests.csproj:4— multi-env-app/src/HRM/HRM.Tests/HRM.Tests.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.
Hollow method — returns a constant without doing the work CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/DependencyInjection.cs:46— `AddRepositories` 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 token-based-auth-core-react/ECommerce/Ordering.Application/DependencyInjection.cs:13— `AddApplication` 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 token-based-auth-core/ECommerce/Ordering.Application/DependencyInjection.cs:13— `AddApplication` 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 token-based-auth-ng/ECommerce/Ordering.Application/DependencyInjection.cs:13— `AddApplication` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
TodoComment CleanArchitectureTemplate/CleanArchitecture/CleanArch.API/Program.cs:82— //TODO: This option must be removed from Production. This invoked to by pass SSL Certificate verification — 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 export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:92— // TODO: Add proper image embedding after fixing the crash — 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 export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:286— // TODO: Re-implement CreateImageParagraph method after fixing Word export issues
Duplicated block (25 lines × 2) REDACTED:61— REDACTED:61-85 | REDACTED:50-74 — before extracting anything, compare `REDACTED` and `REDACTED` 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 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) REDACTED:50— REDACTED:50-74 | REDACTED:112-136 — 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 (25 lines × 2) REDACTED:53— REDACTED:53-77 | REDACTED:53-77 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (15 lines × 2) saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:44— saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:44-58 | saga-choreography-v02/Order.API/Services/PaymentResponseListener.cs:47-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:44` 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 (15 lines × 2) REDACTED:98— REDACTED:98-112 | REDACTED:98-112 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (15 lines × 2) IdempotentDemo/Accounting.API/Utility/HashGenerator.cs:18— IdempotentDemo/Accounting.API/Utility/HashGenerator.cs:18-32 | dotnet-core-nuget-github/CryptoEngine/CryptoGenerator.cs:10-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:42— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:42-57 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:42-57 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:42-57 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:42-57 — before extracting anything, compare `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs` and `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:61— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:61-76 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:61-76 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:61-76 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:61-76 — before extracting anything, compare `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs` and `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/CreateCustomerHandler.cs:18— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/CreateCustomerHandler.cs:18-33 | token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:20-44 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:20-44 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:20-44 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 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 `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:20` 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. 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 × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Commands/EditCustomerCommand.cs:8— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Commands/EditCustomerCommand.cs:8-16 | token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:11-19 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:11-19 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:11-19 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.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 `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Commands/EditCustomerCommand.cs:8` 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 × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/QueryHandlers/GetCustomerByEmailHandler.cs:16— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/QueryHandlers/GetCustomerByEmailHandler.cs:16-24 | token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:12-31 | token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:12-31 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:12-31 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:12` 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 (9 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/QueryHandlers/GetCustomerByIdHandler.cs:16— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/QueryHandlers/GetCustomerByIdHandler.cs:16-24 | token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:13-32 | token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:13-32 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:13-32 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:13` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 4) REDACTED:21— REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) REDACTED:21— REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 — before extracting anything, compare `REDACTED` and `REDACTED` 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 (11 lines × 4) REDACTED:92— REDACTED:92-102 | REDACTED:85-95 | REDACTED:92-102 | REDACTED:87-97 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 3) REDACTED:21— REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 — before extracting anything, compare `REDACTED` and `REDACTED` 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 (11 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserQuery.cs:20— token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserQuery.cs:20-30 | token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetUserQuery.cs:20-30 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/User/GetUserQuery.cs:25-35 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetUserQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetUserQuery.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 (11 lines × 3) REDACTED:92— REDACTED:92-102 | REDACTED:92-102 | REDACTED:87-97 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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.
Non-idempotent mutation: Role.RoleDeleteCommandHandler.Handle MultiTenant/MTShop.Application/Commands/Role/RoleDeleteCommand.cs:19— `Role.RoleDeleteCommandHandler.Handle` mutates persistent state (a repository write one hop away, in IdentityService.DeleteRoleAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Non-idempotent mutation: CatalogItems.CreateCatalogItemCommandHandler.Handle EventSourcing/Application/Commands/CatalogItems/CreateCatalogItemCommand.cs:55— `CatalogItems.CreateCatalogItemCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Non-idempotent mutation: Services.ProductEventHandler.Handle MicroservicesDemo/src/Services/OrderService/OrderService/Services/ProductEventHandler.cs:19— `Services.ProductEventHandler.Handle` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Sync-over-async (deadlock risk) through `.Result` saga-choreography-v02/Payment.API/Services/InventoryReservedListener.cs:90— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:132— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:170— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
D17 · Explicit Debt· Whole file has no live code · ×2
Whole file has no live code — 6 debt markers inside it token-based-auth-core-react/ECommerce/Ordering.Application/Common/Security/TokenGenerator.cs:1— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 6 debt markers (6 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 6 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 6 debt markers inside it token-based-auth-ng/ECommerce/Ordering.Application/Common/Security/TokenGenerator.cs:1— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 6 debt markers (6 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 6 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Cross-context type Customer (Ordering → DapperDemo) REDACTED:27— Customer (context Ordering) is exposed in DapperDemo's public surface via CustomerController.Get — couples the contexts.
Cross-context type Customer (Ordering → DapperDemo) REDACTED:41— Customer (context Ordering) is exposed in DapperDemo's public surface via CustomerController.GetByEmail — couples the contexts.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) REDACTED:50— REDACTED:50-75 | REDACTED:45-70 | REDACTED:43-68 | REDACTED:50-75 | REDACTED:52-77 | REDACTED:45-70 — 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:20— AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:20-59 | AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:131-166 | AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:169-201 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:17-57 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:131-168 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:171-199 — 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 (26 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:27— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:27-52 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:27-52 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:27-52 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.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 (26 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:18— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:18-43 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:18-43 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:18-43 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/EditCustomerHandler.cs:26— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/EditCustomerHandler.cs:26-46 | token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:33-53 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:33-53 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:33-53 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.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 (21 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Command/Base/CommandRepository.cs:18— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Command/Base/CommandRepository.cs:18-38 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Command/Base/CommandRepository.cs:18-38 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Repository/Command/Base/CommandRepository.cs:18-38 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Repository/Command/Base/CommandRepository.cs:18-38 — before extracting anything, compare `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Command/Base/CommandRepository.cs` and `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Command/Base/CommandRepository.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 (19 lines × 2) EventSourcing/Application/Common/DTOs/CreateCatalogItemDTO.cs:7— EventSourcing/Application/Common/DTOs/CreateCatalogItemDTO.cs:7-25 | EventSourcing/Application/Common/DTOs/UpdateCatalogItemDTO.cs:7-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 2) saga-choreography-v02/Catalog.API/Program.cs:13— saga-choreography-v02/Catalog.API/Program.cs:13-31 | saga-choreography-v02/Order.API/Program.cs:13-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. Read the line range as the matched WINDOW rather than a finished unit: at `saga-choreography-v02/Catalog.API/Program.cs:13` 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 × 3) multi-env-app/src/HRM/HRM.API/DTOs/EmployeeDto.cs:22— multi-env-app/src/HRM/HRM.API/DTOs/EmployeeDto.cs:22-39 | multi-env-app/src/HRM/HRM.API/DTOs/EmployeeDto.cs:52-69 | multi-env-app/src/HRM/HRM.API/Models/Employee.cs:11-28 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (18 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Auth/AuthCommand.cs:27— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Auth/AuthCommand.cs:27-44 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Auth/AuthCommand.cs:27-44 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Auth/AuthCommand.cs:27-44 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Auth/AuthCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Auth/AuthCommand.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 (13 lines × 4) MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:55— MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:55-67 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:30-42 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:30-42 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:30-42 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.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 `MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:55` 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 `userDetails` to `DateTime) GenerateJwtToken((string userId, string userName, IList<string> roles)` in one and `(string userId, string userName, IList<string> roles)` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Mapper/CustomerMapper.cs:6— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Mapper/CustomerMapper.cs:6-18 | token-based-auth-core-react/ECommerce/Ordering.Application/Mapper/CustomerMapper.cs:6-18 | token-based-auth-core/ECommerce/Ordering.Application/Mapper/CustomerMapper.cs:6-18 | token-based-auth-ng/ECommerce/Ordering.Application/Mapper/CustomerMapper.cs:6-18 — before extracting anything, compare `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Mapper/CustomerMapper.cs` and `token-based-auth-core-react/ECommerce/Ordering.Application/Mapper/CustomerMapper.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 `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Mapper/CustomerMapper.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 × 4) api-gateway-ocelot/APIGateway/Catalog.API/Model/Product.cs:6— api-gateway-ocelot/APIGateway/Catalog.API/Model/Product.cs:6-19 | kubernetes-demo/KubernetesDemo/Catalog.API/Models/Product.cs:6-19 | ocelot-swagger/APIGateway/Catalog.API/Model/Product.cs:6-19 | service-mesh/ServiceMesh/Catalog.API/Model/Product.cs:6-19 — before extracting anything, compare `api-gateway-ocelot/APIGateway/Catalog.API/Model/Product.cs` and `ocelot-swagger/APIGateway/Catalog.API/Model/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 `api-gateway-ocelot/APIGateway/Catalog.API/Model/Product.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 × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:25— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:25-38 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:25-38 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:25-38 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs:25-38 — before extracting anything, compare `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs` and `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Repository/Query/CustomerQueryRepository.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 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 (14 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:18— token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:18-31 | token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:18-31 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:18-31 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByEmailQuery.cs:18` 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 × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:19— token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:19-32 | token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:19-32 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:19-32 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/Customers/GetCustomerByIdQuery.cs:19` 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) hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:18— hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:18-27 | jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs:18-27 — before extracting anything, compare `hrm/HRM/HRM.API/Repository/EmployeeRepository.cs` and `jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs` as WHOLE FILES: this scan already matched 5 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 (10 lines × 2) hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:31— hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:31-40 | jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs:31-40 — before extracting anything, compare `hrm/HRM/HRM.API/Repository/EmployeeRepository.cs` and `jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs` as WHOLE FILES: this scan already matched 5 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.
DM7 · Repository granularity· Repository for a non-root entity · ×2
Repository for a non-root entity: ICustomerCommandRepository → Customer token-based-auth-core-react/ECommerce/Ordering.Core/Repositories/Command/ICustomerCommandRepository.cs:7— `ICustomerCommandRepository` is a repository over `Customer`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Customer` through its owning aggregate instead.
Repository for a non-root entity: CustomerRepository → Customer DapperDemo/DapperDemo/Customer.API/Repositories/CustomerRepository.cs:12— `CustomerRepository` is a repository over `Customer`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `Customer` through its owning aggregate instead.
Forked directory tree (12 identical files, ~226 lines × 2 trees) micro-frontend/customer-frontend/README.md:1— micro-frontend/customer-frontend/ and micro-frontend/header-frontend/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~226 lines; the trees hold 23 and 18 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Forked directory tree (12 identical files, ~226 lines × 2 trees) micro-frontend/header-frontend/README.md:1— micro-frontend/header-frontend/ and micro-frontend/product-frontend/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~226 lines; the trees hold 18 and 26 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Duplicated block (24 lines × 2 locations) react-redux-toolkit/redux-app/src/components/product/AddProduct.js:43— react-redux-toolkit/redux-app/src/components/product/AddProduct.js:43 · react-redux-toolkit/redux-app/src/components/product/EditProduct.js:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) REDACTED:6— REDACTED:6 · REDACTED:76 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2 locations) micro-frontend/product-frontend/src/components/CategoryComponent/CategoryListComponent.js:5— micro-frontend/product-frontend/src/components/CategoryComponent/CategoryListComponent.js:5 · micro-frontend/product-frontend/src/components/ProductComponent/ProductListComponent.js:5 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (16 lines × 2 locations) react-redux-toolkit/redux-app/src/services/CustomerService.js:4— react-redux-toolkit/redux-app/src/services/CustomerService.js:4 · react-redux-toolkit/redux-app/src/services/ProductService.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (14 lines × 2 locations) micro-frontend/customer-frontend/src/components/CustomerComponent/DataTableComponent.js:46— micro-frontend/customer-frontend/src/components/CustomerComponent/DataTableComponent.js:46 · micro-frontend/product-frontend/src/components/ProductComponent/DataTableComponent.js:56 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (14 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Role/CreateRole.js:32— token-based-auth-core-react/ecommerce.client/src/components/Role/CreateRole.js:32 · token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:59 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (13 lines × 2 locations) react-redux-toolkit/redux-app/src/components/product/EditProduct.js:68— react-redux-toolkit/redux-app/src/components/product/EditProduct.js:68 · react-redux-toolkit/redux-app/src/components/product/EditProduct.js:91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:41— token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:41 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:103 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Auth/Login.js:19— token-based-auth-core-react/ecommerce.client/src/components/Auth/Login.js:19 · token-based-auth-core-react/ecommerce.client/src/components/User/UpdateUser.js:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:71— token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:71 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
X18 · Disposal-pattern correctness· Disposes a dependency it does not own · ×2
Disposes a dependency it does not own MultiTenant/MTShop.Infrastructure/Implementations/Admin/ManageTenantRepository.cs:76— `_adminDbContext` is never created by `ManageTenantRepository` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 76). Its declared type `AdminDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own MultiTenant/MTShop.Infrastructure/Persistence/UnitOfWork.cs:91— `_multitenantDbContext` is never created by `UnitOfWork` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 91). Its declared type `MultitenantDbContext` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 10 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
Stateful singleton: KafkaEventBus MicroservicesDemo/src/Shared/EventBus/EventBus/KafkaEventBus.cs:8— `KafkaEventBus` is a singleton (one shared instance) but mutates instance state outside any lock (_handlers, _subscribedTopics, _isConsuming; e.g. `_handlers` at line 69).
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: HRM.Test jenkins-demo/HRM/HRM.Test/UnitTest1.cs:7— No conventional assertion call was detected in 1 of 1 tests in `HRM.Test` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Build failed — The target solution did not build cleanly (errors: 4), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS1031: Type expected; CS1001: Identifier expected; CS1003: Syntax error, ',' expected.
AdminDbContextInitializer.TrySeedAsync (cognitive 28) MultiTenant/MTShop.Infrastructure/Seed/AdminDbContextInitializer.cs:47— AdminDbContextInitializer.TrySeedAsync has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultitenantDbContextInitializer.TrySeedAsync (cognitive 22) MultiTenant/MTShop.Infrastructure/Seed/MultitenantDbContextInitializer.cs:40— MultitenantDbContextInitializer.TrySeedAsync has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: HrmDbContext.OnModelCreating multi-env-app/src/HRM/HRM.API/Data/HrmDbContext.cs:15— MethodTooLong — OnModelCreating runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TooManyMethods: QueryRepository CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs— TooManyMethods — 206 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:51— MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:51-77 | MultiTenant/MTShop.Application/Commands/Auth/AuthCommand.cs:51-76 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:26-52 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:26-52 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/TokenGenerator.cs:26-52 — These 5 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 5 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 5 times.
Duplicated block (166–171 lines × 2) CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs:104— CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs:104-274 | CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs:359-524 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (50 lines × 2) hrm/HRM/HRM.API/Db/SeedDataGenerator.cs:10— hrm/HRM/HRM.API/Db/SeedDataGenerator.cs:10-59 | jenkins-demo/HRM/HRM.API/Db/SeedDataGenerator.cs:10-59 — before extracting anything, compare `hrm/HRM/HRM.API/Db/SeedDataGenerator.cs` and `jenkins-demo/HRM/HRM.API/Db/SeedDataGenerator.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 × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:25— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:25-62 | token-based-auth-core/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:25-62 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:25-62 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/DependencyInjection.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/DependencyInjection.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 (27–31 lines × 2) PrivateRegistryDemo/PrivateRegistryDemo/Program.cs:8— PrivateRegistryDemo/PrivateRegistryDemo/Program.cs:8-34 | aks-hrm/HRM.API/Program.cs:13-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `aks-hrm/HRM.API/Program.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, `aks-hrm/HRM.API/Program.cs:13` calls `GetConnectionString` and `PrivateRegistryDemo/PrivateRegistryDemo/Program.cs:8` does not — after which the two agree again for 5 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 (27 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:3— token-based-auth-core-react/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:3-29 | token-based-auth-core/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:3-29 | token-based-auth-ng/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:9-35 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.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 (26 lines × 2) multi-env-app/src/HRM/HRM.API/DTOs/EmployeeDto.cs:22— multi-env-app/src/HRM/HRM.API/DTOs/EmployeeDto.cs:22-47 | multi-env-app/src/HRM/HRM.API/DTOs/EmployeeDto.cs:52-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (25 lines × 6) REDACTED:51— REDACTED:51-75 | REDACTED:46-70 | REDACTED:44-68 | REDACTED:51-75 | REDACTED:53-77 | REDACTED:46-70 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `product` to `Product` in one and `Product.API.Model.Product` 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 (25 lines × 3) REDACTED:51— REDACTED:51-75 | REDACTED:51-75 | REDACTED:46-70 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 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–26 lines × 2) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:104— AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:104-128 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:103-128 — before extracting anything, compare `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs` and `ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.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 `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:104` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:132` calls `GetProduct` and `ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:133` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–26 lines × 2) export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:83— export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:83-108 | export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:113-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:113` 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 after the matched lines, `export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:111` calls `WriteLine` and `export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:124` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24 lines × 2) hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:44— hrm/HRM/HRM.API/Repository/EmployeeRepository.cs:44-67 | jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs:44-67 — before extracting anything, compare `hrm/HRM/HRM.API/Repository/EmployeeRepository.cs` and `jenkins-demo/HRM/HRM.API/Repository/EmployeeRepository.cs` as WHOLE FILES: this scan already matched 5 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 (21 lines × 2) grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:47— grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:47-67 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:97-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:47` 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 (22–23 lines × 2) MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:55— MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:55-77 | MultiTenant/MTShop.Application/Commands/Auth/AuthCommand.cs:55-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `MultiTenant/MTShop.Application/Commands/Auth/AdminAuthCommand.cs:55` 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 `userDetails` to `DateTime) GenerateJwtToken((string userId, string userName, IList<string> roles)` in one and `DateTime) GenerateJwtToken((string userId, string userName, string tenantId, IList<string> roles)` 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 (22 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/NotFoundException.cs:3— token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/NotFoundException.cs:3-24 | token-based-auth-core/ECommerce/Ordering.Application/Common/Exceptions/NotFoundException.cs:3-24 | token-based-auth-ng/ECommerce/Ordering.Application/Common/Exceptions/NotFoundException.cs:9-30 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/NotFoundException.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Common/Exceptions/NotFoundException.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/NotFoundException.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 (18–22 lines × 2) EventSourcing/Infrastructure/Persistance/AggregateRepository.cs:47— EventSourcing/Infrastructure/Persistance/AggregateRepository.cs:47-64 | EventSourcing/Infrastructure/Persistance/AggregateRepository.cs:97-118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `EventSourcing/Infrastructure/Persistance/AggregateRepository.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20–21 lines × 2) grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:33— grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:33-53 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:154-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–19 lines × 5) EventSourcing/Application/Commands/CatalogItems/CreateCatalogItemCommand.cs:22— EventSourcing/Application/Commands/CatalogItems/CreateCatalogItemCommand.cs:22-40 | EventSourcing/Application/Commands/CatalogItems/UpdateCatalogItemCommand.cs:25-43 | EventSourcing/Domain/Entities/CatalogItem.cs:46-64 | EventSourcing/Domain/Events/CatalogItem/CatalogItemCreated.cs:31-44 | EventSourcing/Domain/Events/CatalogItem/CatalogItemUpdated.cs:28-41 — before extracting anything, compare `EventSourcing/Domain/Events/CatalogItem/CatalogItemCreated.cs` and `EventSourcing/Domain/Events/CatalogItem/CatalogItemUpdated.cs` as WHOLE FILES: 90% 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. 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 (18 lines × 4) MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:37— MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:37-54 | token-based-auth-core-react/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:33-50 | token-based-auth-core/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:33-50 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/DependencyInjection.cs:33-50 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/DependencyInjection.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/DependencyInjection.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 (14 lines × 2) CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Exceptions/NotFoundException.cs:10— CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Exceptions/NotFoundException.cs:10-23 | MultiTenant/MTShop.Application/Common/Exceptions/NotFoundException.cs:9-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.
Duplicated block (17 lines × 2) REDACTED:65— REDACTED:65-83 | REDACTED:124-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–16 lines × 2) saga-choreography/ECommerce/Catalog.API/Startup.cs:25— saga-choreography/ECommerce/Catalog.API/Startup.cs:25-37 | saga-choreography/ECommerce/Ordering.API/Startup.cs:25-40 — 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 `saga-choreography/ECommerce/Catalog.API/Startup.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 (14–15 lines × 2) AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:21— AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:21-34 | AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:184-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:21` 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 (13–14 lines × 3) AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:22— AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:22-34 | AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:105-117 | AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:185-198 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10–14 lines × 2) api-gateway-ocelot-qos/Catalog.API/Model/CatalogItem.cs:6— api-gateway-ocelot-qos/Catalog.API/Model/CatalogItem.cs:6-19 | saga-choreography/ECommerce/Catalog.API/Models/CatalogItem.cs:6-15 — 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 `api-gateway-ocelot-qos/Catalog.API/Model/CatalogItem.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 (12 lines × 5) api-gateway-ocelot-qos/Catalog.API/Model/CatalogItem.cs:8— api-gateway-ocelot-qos/Catalog.API/Model/CatalogItem.cs:8-19 | api-gateway-ocelot/APIGateway/Catalog.API/Model/Product.cs:8-19 | kubernetes-demo/KubernetesDemo/Catalog.API/Models/Product.cs:8-19 | ocelot-swagger/APIGateway/Catalog.API/Model/Product.cs:8-19 | service-mesh/ServiceMesh/Catalog.API/Model/Product.cs:8-19 — before extracting anything, compare `api-gateway-ocelot-qos/Catalog.API/Model/CatalogItem.cs` and `api-gateway-ocelot/APIGateway/Catalog.API/Model/Product.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.
Duplicated block (10 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:111— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:111-120 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:111-120 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:111-120 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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–11 lines × 3) grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:35— grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:35-45 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:157-165 | grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:297-305 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:291` calls `SetValue`, `NotFound` and `grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:33` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–10 lines × 2) ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:17— ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:17-25 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:131-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) MicroservicesDemo/src/Services/OrderService/OrderService/Data/OrderContext.cs:27— MicroservicesDemo/src/Services/OrderService/OrderService/Data/OrderContext.cs:27-35 | MicroservicesDemo/src/Services/ProductService/ProductService/Data/ProductContext.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. Read the line range as the matched WINDOW rather than a finished unit: at `MicroservicesDemo/src/Services/OrderService/OrderService/Data/OrderContext.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.
Duplicated block (7 lines × 6) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:21— AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:21-27 | AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:134-140 | AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:172-178 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:18-24 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:133-139 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:172-178 — before extracting anything, compare `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs` and `ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.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 `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:21` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:132` calls `GetProduct` and `ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:131` 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 (8 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Commands/CreateCustomerCommand.cs:8— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Commands/CreateCustomerCommand.cs:8-15 | token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:10-17 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:10-17 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:10-17 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 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 `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Commands/CreateCustomerCommand.cs:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:70— AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:70-74 | ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:68-72 — before extracting anything, compare `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs` and `ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.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 `AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) MultiTenant/MTShop.Application/Interfaces/Admin/IAdminIdentityService.cs:13— MultiTenant/MTShop.Application/Interfaces/Admin/IAdminIdentityService.cs:13-18 | MultiTenant/MTShop.Application/Interfaces/IIdentityService.cs:13-18 — 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 that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.API/Program.cs:13— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.API/Program.cs:13-18 | DapperDemo/DapperDemo/Customer.API/Program.cs:13-18 | saga-choreography/ECommerce/Catalog.API/Program.cs:19-24 | saga-choreography/ECommerce/Ordering.API/Program.cs:19-24 — before extracting anything, compare `CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.API/Program.cs` and `DapperDemo/DapperDemo/Customer.API/Program.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 (20 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/DeleteCustomerHandler.cs:17— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Handlers/CommandHandler/DeleteCustomerHandler.cs:17-36 | token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:13-43 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:13-43 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:13-43 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.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 `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Delete/DeleteCustomerCommand.cs:13` 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. 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 × 5) CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Exceptions/ValidationException.cs:9— CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Exceptions/ValidationException.cs:9-19 | MultiTenant/MTShop.Application/Common/Exceptions/ValidationException.cs:11-25 | token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs:10-27 | token-based-auth-core/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs:10-27 | token-based-auth-ng/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs:15-32 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.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 (15 lines × 4) MultiTenant/MTShop.Application/Common/Exceptions/ValidationException.cs:11— MultiTenant/MTShop.Application/Common/Exceptions/ValidationException.cs:11-25 | token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs:10-27 | token-based-auth-core/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs:10-27 | token-based-auth-ng/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs:15-32 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Common/Exceptions/ValidationException.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 (11 lines × 6) REDACTED:21— REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 | REDACTED:21-31 — before extracting anything, compare `REDACTED` and `REDACTED` 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 (78 lines × 2) REDACTED:19— REDACTED:19-96 | REDACTED:19-96 — before extracting anything, compare `REDACTED` and `REDACTED` 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 (59 lines × 2) hrm/HRM/HRM.API/Services/EmployeeService.cs:14— hrm/HRM/HRM.API/Services/EmployeeService.cs:14-72 | jenkins-demo/HRM/HRM.API/Services/EmployeeService.cs:14-72 — before extracting anything, compare `hrm/HRM/HRM.API/Services/EmployeeService.cs` and `jenkins-demo/HRM/HRM.API/Services/EmployeeService.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 (67 lines × 3) token-based-auth-core-react/ECommerce/Ordering.API/Controllers/CustomerController.cs:34— token-based-auth-core-react/ECommerce/Ordering.API/Controllers/CustomerController.cs:34-100 | token-based-auth-core/ECommerce/Ordering.API/Controllers/CustomerController.cs:34-100 | token-based-auth-ng/ECommerce/Ordering.API/Controllers/CustomerController.cs:34-100 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.API/Controllers/CustomerController.cs` and `token-based-auth-core/ECommerce/Ordering.API/Controllers/CustomerController.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 (47 lines × 3) token-based-auth-core-react/ECommerce/Ordering.API/Controllers/RoleController.cs:26— token-based-auth-core-react/ECommerce/Ordering.API/Controllers/RoleController.cs:26-72 | token-based-auth-core/ECommerce/Ordering.API/Controllers/RoleController.cs:26-72 | token-based-auth-ng/ECommerce/Ordering.API/Controllers/RoleController.cs:26-72 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.API/Controllers/RoleController.cs` and `token-based-auth-core/ECommerce/Ordering.API/Controllers/RoleController.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 (79 lines × 3) token-based-auth-core-react/ECommerce/Ordering.API/Controllers/UserController.cs:29— token-based-auth-core-react/ECommerce/Ordering.API/Controllers/UserController.cs:29-107 | REDACTED:31-109 | token-based-auth-ng/ECommerce/Ordering.API/Controllers/UserController.cs:29-107 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.API/Controllers/UserController.cs` and `REDACTED` 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.
Duplicated block (20 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:25— token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:25-44 | token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:25-44 | token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs:25-44 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 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 `token-based-auth-core-react/ECommerce/Ordering.Application/Commands/Customers/Create/CreateCustomerCommand.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. 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 (19 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetAllUsersDetailsQuery.cs:21— token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetAllUsersDetailsQuery.cs:21-39 | token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetAllUsersDetailsQuery.cs:21-39 | token-based-auth-ng/ECommerce/Ordering.Application/Queries/User/GetAllUsersDetailsQuery.cs:26-44 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Queries/User/GetAllUsersDetailsQuery.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Queries/User/GetAllUsersDetailsQuery.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 (5 lines × 4) CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Mapper/OrderingMappingProfile.cs:11— CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Mapper/OrderingMappingProfile.cs:11-15 | token-based-auth-core-react/ECommerce/Ordering.Application/Mapper/OrderingMappingProfile.cs:12-16 | token-based-auth-core/ECommerce/Ordering.Application/Mapper/OrderingMappingProfile.cs:12-16 | token-based-auth-ng/ECommerce/Ordering.Application/Mapper/OrderingMappingProfile.cs:12-16 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Application/Mapper/OrderingMappingProfile.cs` and `token-based-auth-core/ECommerce/Ordering.Application/Mapper/OrderingMappingProfile.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 (21 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:49— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:49-69 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:49-69 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:49-69 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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 (15 lines × 3) token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:93— token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:93-107 | token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:93-107 | token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:93-107 — before extracting anything, compare `token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` and `token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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.
PII in event: OrderCreatedEvent MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:3— Persisted event carries personal data (CustomerEmail) — no crypto-shredding strategy covers it, so it collides with the GDPR right-to-erasure.
Outbound HTTP without resilience CacheRefreshFunction/CacheRefreshAzureFunction/CacheRefreshTimerTriggerFunction.cs:14— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Forked directory tree (14 identical files, ~233 lines × 2 trees) micro-frontend/customer-frontend/README.md:1— micro-frontend/customer-frontend/ and micro-frontend/product-frontend/ are near-verbatim copies of each other: 14 files are byte-identical under the same relative paths (~233 lines; the trees hold 23 and 26 files). That is one structural fact, not 14 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Forked directory tree (10 identical files, ~204 lines × 2 trees) micro-frontend/header-frontend/README.md:1— micro-frontend/header-frontend/ and react-redux-toolkit/redux-app/ are near-verbatim copies of each other: 10 files are byte-identical under the same relative paths (~204 lines; the trees hold 18 and 32 files). That is one structural fact, not 10 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Duplication concentrated across 5 sibling directories (12 clone groups) token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:29— 12 duplicated blocks under token-based-auth-core-react/ecommerce.client/src/components/ have copies in at least two of the sibling directories Auth, Customer, Role, User, UsersRoles — 8 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (8 clone groups) micro-frontend/customer-frontend/config-overrides.js:2— 8 duplicated blocks under micro-frontend/ have copies in at least two of the sibling directories customer-frontend, header-frontend, product-frontend — 4 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (103 matched lines × 2 locations) · ×1
Duplicated block with local edits (103 matched lines × 2 locations) react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:9— react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:9 · react-redux-toolkit/redux-app/src/components/product/EditProduct.js:9 — the two spans are one implementation copied and then locally edited — 465 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) react-redux-toolkit/redux-app/src/components/customer/CustomerList.js:19— react-redux-toolkit/redux-app/src/components/customer/CustomerList.js:19 · react-redux-toolkit/redux-app/src/components/product/ProductsList.js:14 — the two spans are one implementation copied and then locally edited — 304 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) react-redux-toolkit/redux-app/src/redux/slices/customersSlice.js:10— react-redux-toolkit/redux-app/src/redux/slices/customersSlice.js:10 · react-redux-toolkit/redux-app/src/redux/slices/productsSlice.js:10 — the two spans are one implementation copied and then locally edited — 303 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (37 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:29— token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:29 · token-based-auth-core-react/ecommerce.client/src/components/User/DeleteUser.js:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (34 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:4— token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:4 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:4 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (33 matched lines × 2 locations) · ×1
Duplicated block with local edits (33 matched lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Role/EditRole.js:28— token-based-auth-core-react/ecommerce.client/src/components/Role/EditRole.js:28 · token-based-auth-core-react/ecommerce.client/src/components/User/UpdateUser.js:43 — the two spans are one implementation copied and then locally edited — 180 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (32 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Role/Roles.js:14— token-based-auth-core-react/ecommerce.client/src/components/Role/Roles.js:14 · token-based-auth-core-react/ecommerce.client/src/components/User/Users.js:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 3 locations) react-redux-toolkit/redux-app/src/components/customer/AddCustomer.js:64— react-redux-toolkit/redux-app/src/components/customer/AddCustomer.js:64 · react-redux-toolkit/redux-app/src/components/customer/AddCustomer.js:101 · react-redux-toolkit/redux-app/src/components/product/AddProduct.js:87 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (22 lines × 2 locations) REDACTED:53— REDACTED:53 · REDACTED:100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/User/DeleteUser.js:18— token-based-auth-core-react/ecommerce.client/src/components/User/DeleteUser.js:18 · token-based-auth-core-react/ecommerce.client/src/components/User/UpdateUser.js:28 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:74— react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:74 · react-redux-toolkit/redux-app/src/components/customer/EditCustomer.js:110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 3 locations) micro-frontend/customer-frontend/config-overrides.js:2— micro-frontend/customer-frontend/config-overrides.js:2 · micro-frontend/header-frontend/config-overrides.js:2 · micro-frontend/product-frontend/config-overrides.js:2 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (11 lines × 6 locations) micro-frontend/customer-frontend/src/reportWebVitals.js:1— micro-frontend/customer-frontend/src/reportWebVitals.js:1 · micro-frontend/header-frontend/src/reportWebVitals.js:1 · micro-frontend/master-frontend/src/reportWebVitals.js:1 · micro-frontend/product-frontend/src/reportWebVitals.js:1 · +2 more site(s) not listed — the 6 copies are spread across 6 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 6 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (11 lines × 2 locations) micro-frontend/header-frontend/src/index.js:19— micro-frontend/header-frontend/src/index.js:19 · micro-frontend/product-frontend/src/index.js:20 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (11 lines × 3 locations) token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:22— token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:22 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:27 · token-based-auth-core-react/ecommerce.client/src/components/UsersRoles/UsersRoles.js:58 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (9 lines × 3 locations) micro-frontend/customer-frontend/src/index.js:8— micro-frontend/customer-frontend/src/index.js:8 · micro-frontend/header-frontend/src/index.js:8 · micro-frontend/product-frontend/src/index.js:8 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (9 lines × 2 locations) micro-frontend/master-frontend/src/App.js:18— micro-frontend/master-frontend/src/App.js:18 · react-redux-toolkit/redux-app/src/App.js:17 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (8 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:72— token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:72 · token-based-auth-core-react/ecommerce.client/src/components/User/CreateUser.js:82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2 locations) token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:16— token-based-auth-core-react/ecommerce.client/src/components/Customer/Create.jsx:16 · token-based-auth-core-react/ecommerce.client/src/components/Role/EditRole.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 4 locations) token-based-auth-core-react/ecommerce.client/src/components/Customer/Customers.jsx:2— token-based-auth-core-react/ecommerce.client/src/components/Customer/Customers.jsx:2 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Delete.jsx:2 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:2 · token-based-auth-core-react/ecommerce.client/src/components/Role/DeleteRole.js:2 — the 4 copies are spread across 4 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited.
Duplicated block (7 lines × 3 locations) token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:115— token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:115 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:124 · token-based-auth-core-react/ecommerce.client/src/components/Customer/Edit.jsx:134 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
No lint or typecheck script — test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~13 LoC) token-based-auth-core-react/ecommerce.client/src/reportWebVitals.js— no import path from any entry point (19 application, 6 tooling, 12 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@mui/styled-engine-sc' — Declared in micro-frontend/customer-frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@testing-library/user-event' — Declared in micro-frontend/customer-frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-bootstrap' — Declared in micro-frontend/customer-frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
async void method: SetTenant MultiTenant/MTShop.Infrastructure/Implementations/TenantService.cs:49— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Blocking `Thread.Sleep` inside an `async` method REDACTED:28— `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×1
Disposable created and abandoned in the method that made it AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ReportingRepository.cs:32— `dt` is a `DataTable`, which implements `IDisposable`, and it is created here (line 32). Every use of it in `GetChangeLogDynamic` 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 dt = …;`), which releases it at the end of the scope on every path including a throw.
X20 · Mistyped argument guard· Argument guard throws the exception its own condition disproves · ×1
Argument guard throws the exception its own condition disproves EventSourcing/Domain/Entities/Common/BaseAggregateRoot.cs:74— The guard on line 73 rejects `events` and line 74 reports that rejection as `ArgumentNullException` — but the condition's own test `!events.Any()` is true of a value that is NOT null: it is satisfied by an EMPTY `events`, and on that path `events` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
X5 · Nullable reference types· Null guard scopes only part of the work it protects · ×1
Null guard scopes only part of the work it protects grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:221— This method contradicts itself about `product`: line 202 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 221 then dereferences `product` as `product.Name` AFTER the block has closed, where the guard no longer applies. A null `product` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `product` truly cannot be null by then, the guard above is misleading and should go.
Orphaned file CleanArchitectureTemplate/CleanArchitecture/CleanArch.Infrastructure/Repository/Query/Base/QueryRepository.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file grafana-dotnet-core/EcommerceApi/Controllers/ProductController.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file AuditLogRawSQL/AuditLog.API/AuditTrail/Implementations/AuditTrail.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MultiTenant/MTShop.Infrastructure/Implementations/AdminIdentityService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file multi-env-app/src/HRM/HRM.API/Data/HrmDbContext.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file export-report-api/ExportReportAPI/Generator/Templates/PDFTemplate.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file multi-env-app/src/HRM/HRM.API/Services/EmployeeService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file export-report-api/ExportReportAPI/Generator/Templates/ExcelTemplate.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file ConcurrencyRawSQL/Concurrency.API/Repositories/Implementations/ProductRepository.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MultiTenant/MTShop.Infrastructure/Implementations/IdentityService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file grafana-dotnet-core/EcommerceApi/Metrics/MetricsRegistry.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file AuditLogRawSQL/AuditLog.API/Repositories/Implementations/ProductRepository.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MicroservicesDemo/src/Services/OrderService/OrderService/Services/ProductEventHandler.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file EventSourcing/Infrastructure/Persistance/AggregateRepository.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file multi-env-app/src/HRM/HRM.API/Services/DepartmentService.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file saga-choreography-v02/Payment.API/Services/InventoryReservedListener.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MicroservicesDemo/src/Shared/EventBus/EventBus/KafkaEventBus.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file asp-azure-key-vault/src/ECommerceApi/Program.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Interpolated log message defeats structured logging MultiTenant/MTShop.API/Middlewares/ExceptionHandlingMiddleware.cs:63— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:59— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:38— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:53— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:62— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/InventoryResponseListener.cs:69— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/PaymentResponseListener.cs:41— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/PaymentResponseListener.cs:56— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/PaymentResponseListener.cs:65— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/PaymentResponseListener.cs:73— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Order.API/Services/PaymentResponseListener.cs:89— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:50— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/InventoryReleaseListener.cs:38— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/InventoryReleaseListener.cs:53— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/InventoryReleaseListener.cs:67— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/OrderCreatedListener.cs:43— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/OrderCreatedListener.cs:69— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/OrderCreatedListener.cs:75— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/OrderCreatedListener.cs:91— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/PaymentConfirmationListener.cs:38— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Catalog.API/Services/PaymentConfirmationListener.cs:51— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Payment.API/Services/InventoryReservedListener.cs:45— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Payment.API/Services/InventoryReservedListener.cs:67— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Payment.API/Services/InventoryReservedListener.cs:110— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging saga-choreography-v02/Payment.API/Services/PaymentProcessor.cs:22— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
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 Archive/ECommerce/Program.cs:7— 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 AuditLogEFPlus/AuditLog.API/Program.cs:10— 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 AuditLogRawSQL/AuditLog.API/Program.cs:10— 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 CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.API/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 ConcurrencyAppToken/ConcurrencyHandling.API/Program.cs:4— 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 ConcurrencyDBToken/ConcurrencyHandling.API/Program.cs:4— 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 ConcurrencyEtags/ConcurrencyHandling.API/Program.cs:4— 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 ConcurrencyHyperMedia/ConcurrencyHandling.API/Program.cs:4— 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 ConcurrencyRawSQL/Concurrency.API/Program.cs:7— 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 DapperDemo/DapperDemo/Customer.API/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 EFBulkBatch/EFBulkBatch/Program.cs:12— 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 EventSourcing/Catalog.API/Program.cs:5— 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 IdempotentDemo/Accounting.API/Program.cs:4— 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 MicroservicesDemo/src/Services/OrderService/OrderService/Program.cs:7— 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 MicroservicesDemo/src/Services/ProductService/ProductService/Program.cs:7— 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 MiddlewareExample/Program.cs:4— 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 MultiTenant/MTShop.API/Program.cs:10— 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 PrivateRegistryDemo/PrivateRegistryDemo/Program.cs:8— 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 aks-hrm/HRM.API/Program.cs:11— 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 api-gateway-ocelot-qos/BFF.Web/Program.cs:7— 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 api-gateway-ocelot-qos/Catalog.API/Program.cs:4— 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 api-gateway-ocelot/APIGateway/BFF.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.
No security response headers detected api-gateway-ocelot/APIGateway/Catalog.API/Program.cs:4— 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 api-gateway-ocelot/APIGateway/Location.API/Program.cs:1— 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.
Commented-out code REDACTED:39— 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 AuditLogEFPlus/AuditLog.API/Program.cs:42— 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 REDACTED:105— 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 REDACTED:104— 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 REDACTED:122— 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 EventSourcing/Application/Commands/CatalogItems/CreateCatalogItemCommand.cs:66— 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 EventSourcing/Application/Common/Resolvers/PrivateSetterContractResolver.cs:27— 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 EventSourcing/Domain/Events/CatalogItem/CatalogItemCreated.cs:17— 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 EventSourcing/Domain/Events/CatalogItem/CatalogItemUpdated.cs:17— 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 EventSourcing/Infrastructure/DependencyInjection.cs:35— 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 REDACTED:103— 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 MultiTenant/MTShop.API/Program.cs:72— 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 MultiTenant/MTShop.Application/Interfaces/Admin/IAdminIdentityService.cs:24— 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 MultiTenant/MTShop.Application/Interfaces/Admin/IManageTenantRepository.cs:10— 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 MultiTenant/MTShop.Application/Interfaces/IIdentityService.cs:24— 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 MultiTenant/MTShop.Application/Queries/Customer/CustomerQuery.cs:23— 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 MultiTenant/MTShop.Infrastructure/Extensions/ServiceCollectionExtensions.cs:138— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:170— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:252— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:25— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:58— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:19— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:3— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
DM2 · Strongly-typed ids· Primitive id on a domain type · ×8
Primitive id on a domain type: Customer.TenantId MultiTenant/MTShop.Core/Entities/Customer.cs:13— `Customer.TenantId` 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: Product.TenantId MultiTenant/MTShop.Core/Entities/Product.cs:12— `Product.TenantId` 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: TenantEntity.TenantKey MultiTenant/MTShop.Core/Entities/Admin/TenantEntity.cs:13— `TenantEntity.TenantKey` 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: UpdateCatalogItemCommand.CatalogItemId EventSourcing/Application/Commands/CatalogItems/UpdateCatalogItemCommand.cs:23— `UpdateCatalogItemCommand.CatalogItemId` 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: OrderCreatedEvent.OrderId MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:5— `OrderCreatedEvent.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: OrderCreatedEvent.ProductId MicroservicesDemo/src/Shared/EventBus/EventBus/Events/OrderCreatedEvent.cs:6— `OrderCreatedEvent.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: ProductCreatedEvent.ProductId MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductCreatedEvent.cs:5— `ProductCreatedEvent.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: ProductUpdatedEvent.ProductId MicroservicesDemo/src/Shared/EventBus/EventBus/Events/ProductUpdatedEvent.cs:5— `ProductUpdatedEvent.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.
Fat interface: IIdentityService (19 members) MultiTenant/MTShop.Application/Interfaces/IIdentityService.cs:6— `IIdentityService` declares 19 members: `CreateUserAsync`, `CreateUserAsync`, `GetUserNameAsync`, `GetUserIdAsync`, `GetUserAsync`, `UpdateUserAsync`, `DeleteUserAsync`, `IsInRoleAsync`, `GetUserRolesAsync`, `SignInUserAsync`, `GetUserDetailsAsync`, `AssignUserToRoleAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetRolesAsync`, `GetRoleAsync`, `CreateRoleAsync`, `UpdateRoleAsync`, `DeleteRoleAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IAdminIdentityService (19 members) MultiTenant/MTShop.Application/Interfaces/Admin/IAdminIdentityService.cs:6— `IAdminIdentityService` declares 19 members: `CreateUserAsync`, `CreateUserAsync`, `GetUserNameAsync`, `GetUserIdAsync`, `GetUserAsync`, `UpdateUserAsync`, `DeleteUserAsync`, `IsInRoleAsync`, `GetUserRolesAsync`, `SignInUserAsync`, `GetUserDetailsAsync`, `AssignUserToRoleAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetRolesAsync`, `GetRoleAsync`, `CreateRoleAsync`, `UpdateRoleAsync`, `DeleteRoleAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 19 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IIdentityService (20 members) token-based-auth-core-react/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:3— `IIdentityService` declares 20 members: `CreateUserAsync`, `SigninUserAsync`, `GetUserIdAsync`, `GetUserDetailsAsync`, `GetUserDetailsByUserNameAsync`, `GetUserNameAsync`, `DeleteUserAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetAllUsersDetailsAsync`, `UpdateUserProfile`, `CreateRoleAsync`, `DeleteRoleAsync`, `GetRolesAsync`, `GetRoleByIdAsync`, `UpdateRole`, `IsInRoleAsync`, `GetUserRolesAsync`, `AssignUserToRole`, `UpdateUsersRole`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IIdentityService (20 members) token-based-auth-ng/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:9— `IIdentityService` declares 20 members: `CreateUserAsync`, `SigninUserAsync`, `GetUserIdAsync`, `GetUserDetailsAsync`, `GetUserDetailsByUserNameAsync`, `GetUserNameAsync`, `DeleteUserAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetAllUsersDetailsAsync`, `UpdateUserProfile`, `CreateRoleAsync`, `DeleteRoleAsync`, `GetRolesAsync`, `GetRoleByIdAsync`, `UpdateRole`, `IsInRoleAsync`, `GetUserRolesAsync`, `AssignUserToRole`, `UpdateUsersRole`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IIdentityService (20 members) token-based-auth-core/ECommerce/Ordering.Application/Common/Interfaces/IIdentityService.cs:3— `IIdentityService` declares 20 members: `CreateUserAsync`, `SigninUserAsync`, `GetUserIdAsync`, `GetUserDetailsAsync`, `GetUserDetailsByUserNameAsync`, `GetUserNameAsync`, `DeleteUserAsync`, `IsUniqueUserName`, `GetAllUsersAsync`, `GetAllUsersDetailsAsync`, `UpdateUserProfile`, `CreateRoleAsync`, `DeleteRoleAsync`, `GetRolesAsync`, `GetRoleByIdAsync`, `UpdateRole`, `IsInRoleAsync`, `GetUserRolesAsync`, `AssignUserToRole`, `UpdateUsersRole`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IQueryRepository<TEntity> (30 members) CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs:6— `IQueryRepository<TEntity>` declares 30 members under just 3 distinct name(s): `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `SingleAsync`, `GetDataTableAsync`, `GetDataTableAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 30 separate responsibilities: a caller binds to 3 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 30 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Duplicated predicate export-report-api/ExportReportAPI/Generator/Templates/ExcelTemplate.cs:38— `additionalInfo != null && additionalInfo.Any()` appears character-identically in 3 files — export-report-api/ExportReportAPI/Generator/Templates/ExcelTemplate.cs, export-report-api/ExportReportAPI/Generator/Templates/PDFTemplate.cs, export-report-api/ExportReportAPI/Generator/Templates/WordTemplate.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 micro-frontend/customer-frontend/src/reportWebVitals.js:2— `onPerfEntry && onPerfEntry instanceof Function` appears character-identically in 6 files — micro-frontend/customer-frontend/src/reportWebVitals.js, micro-frontend/header-frontend/src/reportWebVitals.js, micro-frontend/master-frontend/src/reportWebVitals.js, micro-frontend/product-frontend/src/reportWebVitals.js. 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 REDACTED:108— `o.ProductId == productId && o.Status == OrderStatus.Pending` appears character-identically in 2 files — REDACTED, MicroservicesDemo/src/Services/OrderService/OrderService/Services/ProductEventHandler.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 token-based-auth-core-react/ECommerce/Ordering.Application/Mapper/CustomerMapper.cs:12— `p.GetMethod.IsPublic || p.GetMethod.IsAssembly` appears character-identically in 4 files — CleanArchitectureDemo/Ecommerce/Services/Ordering/Ordering.Application/Mapper/CustomerMapper.cs, token-based-auth-core-react/ECommerce/Ordering.Application/Mapper/CustomerMapper.cs, token-based-auth-core/ECommerce/Ordering.Application/Mapper/CustomerMapper.cs, token-based-auth-ng/ECommerce/Ordering.Application/Mapper/CustomerMapper.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 MultiTenant/MTShop.Infrastructure/Implementations/AdminIdentityService.cs:135— `user.UserName == "admin" || user.UserName == "maidul"` appears character-identically in 2 files — MultiTenant/MTShop.Infrastructure/Implementations/AdminIdentityService.cs, MultiTenant/MTShop.Infrastructure/Implementations/IdentityService.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 token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs:100— `user.UserName == "system" || user.UserName == "admin"` appears character-identically in 3 files — token-based-auth-core-react/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs, token-based-auth-core/ECommerce/Ordering.Infrastructure/Services/IdentityService.cs, token-based-auth-ng/ECommerce/Ordering.Infrastructure/Services/IdentityService.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.
ED3 · Event naming· Event not named in past tense · ×4
Event not named in past tense: BaseDomainEvent EventSourcing/Domain/Entities/Common/BaseDomainEvent.cs:8— `BaseDomainEvent` 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: CreateCatalogItemCommand EventSourcing/Application/Commands/CatalogItems/CreateCatalogItemCommand.cs:7— `CreateCatalogItemCommand` 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: DeleteCatalogItemCommand EventSourcing/Application/Commands/CatalogItems/DeleteCatalogItemCommand.cs:7— `DeleteCatalogItemCommand` 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: UpdateCatalogItemCommand EventSourcing/Application/Commands/CatalogItems/UpdateCatalogItemCommand.cs:7— `UpdateCatalogItemCommand` 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.
Pass-through layer AuditLogRawSQL/AuditLog.API/Services/Implementations/ProductService.cs:7— ProductService: all 5 public methods forward their arguments unchanged to _productRepository and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _productRepository directly, or give the layer a job.
Pass-through layer DapperDemo/DapperDemo/Customer.API/Services/CustomerService.cs:9— CustomerService: all 7 public methods forward their arguments unchanged to _customerRepository and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _customerRepository directly, or give the layer a job.
Pass-through layer ConcurrencyRawSQL/Concurrency.API/Services/Implementations/ProductService.cs:7— ProductService: all 5 public methods forward their arguments unchanged to _productRepository and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _productRepository directly, or give the layer a job.
redundant comment token-based-auth-ng/ECommerce/Ordering.Application/Commands/Customers/Update/EditCustomerCommand.cs:10— "Customer create command with CustomerResponse" — delete - the class name 'EditCustomerCommand' already conveys this
redundant comment token-based-auth-ng/ECommerce/Ordering.Application/DTOs/CustomerResponse.cs:5— "Customer response or DTO class" — delete - CustomerResponse already says this
C5 · Data-Subject Rights· Partial data-subject-rights support · ×1
Partial data-subject-rights support — Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
D21 · Naming Consistency· Inconsistent namespace casing for the 'ECommerce' module. Some namespaces use 'ECommerceApi' (CamelCase for the acronym) while others use 'EcommerceApi' (lowercase 'c'). Additionally, the DbContext types are named inconsistently · ×1
Inconsistent namespace casing for the 'ECommerce' module. Some namespaces use 'ECommerceApi' (CamelCase for the acronym) while others use 'EcommerceApi' (lowercase 'c'). Additionally, the DbContext types are named inconsistently: 'AppDbContext' vs 'EcommerceDbContext'. — Standardize the acronym casing to 'ECommerce' across all namespaces and types, and ensure DbContext names follow a consistent pattern (e.g., always 'AppDbContext' or always '<Module>DbContext'). (symbols: ECommerceApi.Models.User, ECommerceApi.Models.OrderItem, ECommerceApi.DTOs.Orders.OrderItemResponseDto, ECommerceApi.DTOs.Orders.OrderItemRequestDto, ECommerceApi.DTOs.Auth.RegisterDto, ECommerceApi.DTOs.Auth.AuthResponseDto, ECommerceApi.Services.IEmailService, ECommerceApi.Repositories.IProductRepository, ECommerceApi.Controllers.OrdersController, ECommerceApi.Controllers.ProductController, ECommerceApi.Controllers.ConfigController, ECommerceApi.Controllers.WeatherForecastController, ECommerceApi.Data.AppDbContext, ECommerceApi.Data.EcommerceDbContext)
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Dormant codebase — 125 of 125 significant files have no living knowledge — the codebase as a whole is dormant, not 125 separate risks. Counted over 125 of the 789 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D34 · Knowledge Freshness· Most significant orphaned file · ×1
Most significant orphaned file CleanArchitectureTemplate/CleanArchitecture/CleanArch.Application/Common/Interfaces/Repositories/Query/Base/IQueryRepository.cs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
DM9 · Scattered domain decisions· Rule about [ProductId, Status] decided in 2 places · ×1
Rule about [ProductId, Status] decided in 2 places — OrderService.Models.Order's [ProductId, Status] are judged in OrderService.Controllers.OrdersController, OrderService.Services.ProductEventHandler — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
IC1 · Incompleteness & stubs· Placeholder data left in code · ×1
Placeholder data left in code ECommerceFacade/ECommerceFacade/Program.cs:98— A placeholder e-mail address ("customer@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.
Thin README — The root README is 2 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
Logging is not universal — Only 44/84 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 84, 69 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
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.
PF2 · Allocation hygiene· No allocation-aware APIs detected · ×1
No allocation-aware APIs detected — No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.
R7 · Dead Code· Unused export 'ErrorToastify' · ×1
Unused export 'ErrorToastify' react-redux-toolkit/redux-app/src/helper/ToastifyMessage.js:17— Nothing imports this binding — it is safe to review for removal.
Unused export 'InfoToastify' react-redux-toolkit/redux-app/src/helper/ToastifyMessage.js:24— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'convertDateFormat' · ×1
Unused export 'convertDateFormat' react-redux-toolkit/redux-app/src/utils/Conversion.js:1— Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene· Test-only dependency '@testing-library/react' in production deps · ×1
Test-only dependency '@testing-library/react' in production deps micro-frontend/customer-frontend/package.json:12— Only test files import it (first: micro-frontend/customer-frontend/src/App.test.js:1) — move it to devDependencies.
OIDC metadata fetched over HTTP MultiTenant/MTShop.API/Program.cs:53— `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 103/574 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.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted MicroservicesDemo/src/Shared/EventBus/EventBus/KafkaEventBus.cs:112— `LogDebug` at line 112 is called with an argument built by `string.Join(", ", _subscribedTopics)` (line 112), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Nullable reference types not enabled everywhere — 92/100 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Off the main sequence: Shared (saga-choreography-v02/Shared) saga-choreography-v02/Shared/Shared.csproj:1— Shared (saga-choreography-v02/Shared): 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: Shared (saga-choreography/ECommerce/Shared) saga-choreography/ECommerce/Shared/Shared.csproj:1— Shared (saga-choreography/ECommerce/Shared): abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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
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 1 file(s) — `dms-azure-blob-aspnet/Controllers/DocumentsController.cs` — 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 — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a161da-132f-79d2-8860-f171123f9b09 · 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 — 149 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: 238 · Warnings: 1043 · Recommendations: 373 · Info: 98 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 04:24 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.