Public report of huynxtb/progcoder-shop-microservices, published 9 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey β
Signed and filed in the standard's public register, 9 November 2026, 02:34 UTC Β· Survey ID cd_2288a2cc8252497db5f8c5b7dd129271
huynxtb/progcoder-shop-microservices
Measured 9 November 2026, 02:33 UTC, at code version ec2480a
Test distribution is not measured: No automated tests.
CAI scoreAt riskUp 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 101,992 lines of product code in 58 projects, tests not counted Β· Estimated rebuild effort: about 1.2 person-years Β· Weakest lens: Production Readiness, 19
Findings by how serious they are
775 critical893 serious395 minor
7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
9 November 2026, 02:33 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology βΈ
117of 117 dimensions measured by tools.
1976of 2063 findings point to an exact file and line, so you can open each one in the code. The other 87 concern the repository as a whole, such as missing documentation.
117dimensions across 9 lenses, read from 101,992 lines of product code in 58 projects.
huynxtb/progcoder-shop-microservices is rated At risk because critical security findings are open. Its score is held back because the project has no automated tests and 227 passwords or keys sit in the current code. It scores 30 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 19, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 8 points. Replacing the 227 exposed passwords or keys and switching the old ones off would lift Production Readiness itself, also worth about 8. Raising Production Readiness to 70 would lift the score to about 38.
228 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. 227 passwords or keys in the code and 103 in the code's history are open to anyone who can read the repository, and sixty-nine known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, replacing each exposed password or key and updating the vulnerable packages would close these risks. Limiting each secret to its own step would fix the 28 secrets exposed to more of the pipeline than needed, and the eight unsafe settings in infrastructure or container files need changing to safe values. The 39 controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 101,992 lines, about β¬180,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 19 to 70, the lowest score rated Strong, the score would rise from 30 to about 38.
Code composition: what the lines of code are
Business logic 18%Supporting code 71%Generated by tools 11%
New since the last survey: 121 findings
These 121 critical or serious findings weren't in the previous survey, on 22 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Handler temporal coupling Β· Temporal coupling in handler: UpsertedProductIntegrationEventHandler.Consume src/Services/Notification/Worker/Notification.Worker.Consumer/EventHandlers/Integrations/UpsertedProductIntegrationEventHandler.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: BrandEntity src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: BrandEntity src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: BrandEntity src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CategoryEntity src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CategoryEntity src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CategoryEntity src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs
Ambient inputs in the domain Β· Domain type reads a global random source: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Catalog/Core/Catalog.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Inventory/Core/Inventory.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Order/Core/Order.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Basket/Core/Basket.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Discount/Core/Discount.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Search/Core/Search.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Notification/Core/Notification.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: IDomainEvent src/Services/Report/Core/Report.Domain/Abstractions/IDomainEvent.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: InventoryItemEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs
Ambient inputs in the domain Β· Domain type reads the wall clock: InventoryItemEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs
Constructible invalid state Β· Constructible in an invalid state: InventoryItemEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs
Constructible invalid state Β· Constructible in an invalid state: InventoryReservationEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs
Constructible invalid state Β· Constructible in an invalid state: LocationEntity src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 1256 findings
These 1256 critical or serious findings were in the previous survey, on 22 October 2026, and are gone from this one. The first 100 are listed here.
β¬60,000 to β¬300,000, for 997 to 3,164 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem
Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 30. 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
Large: 101,992 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at β¬60 to β¬95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No tests found finding(s) in Test Distribution.
Raises the score by about 8 points Β· Low effort Β· Test Distribution
2
Resolve the 3 Banned license finding(s) in License Compliance β start with REDACTED (2).
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed Β· Value at risk
This code would cost about β¬180,000 to build again, about 1.2 person-years of work. Its weakest lens is Production Readiness, at 19 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 58 Domain Modelling findings Β· Common cause
58 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. 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 (18 findings) · Strongly-typed ids (40 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first Β· First action
Resolve the 1 No tests found finding(s) in Test Distribution. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 Test Distribution findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year Β· Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 523 lines over the last 90 days, which is about 2,121 lines a year. At that pace, the extra work comes to an estimated 0.1 to 0.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
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.
470 modules, with 389 dependencies between them. 2 loops run through 6 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 430 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.
Basket.Application.Repositories uses Basket.Domain.Entities, so a change to Basket.Domain.Entities can break Basket.Application.Repositories, while a change to Basket.Application.Repositories can't break Basket.Domain.Entities.
Position
Below the diagonal: Basket.Application.Repositories uses a module listed above it, which is the healthy direction.
BuildingBlocks.Pagination uses Common.Models, so a change to Common.Models can break BuildingBlocks.Pagination, while a change to BuildingBlocks.Pagination can't break Common.Models.
Position
Below the diagonal: BuildingBlocks.Pagination uses a module listed above it, which is the healthy direction.
Catalog.Application.Dtos.Products uses Common.Models, so a change to Common.Models can break Catalog.Application.Dtos.Products, while a change to Catalog.Application.Dtos.Products can't break Common.Models.
Position
Below the diagonal: Catalog.Application.Dtos.Products uses a module listed above it, which is the healthy direction.
Common.Models.Reponses uses Common.Models, so a change to Common.Models can break Common.Models.Reponses, while a change to Common.Models.Reponses can't break Common.Models.
Position
Below the diagonal: Common.Models.Reponses uses a module listed above it, which is the healthy direction.
Discount.Application.Dtos.Coupons uses Discount.Domain.Enums, so a change to Discount.Domain.Enums can break Discount.Application.Dtos.Coupons, while a change to Discount.Application.Dtos.Coupons can't break Discount.Domain.Enums.
Position
Below the diagonal: Discount.Application.Dtos.Coupons uses a module listed above it, which is the healthy direction.
Discount.Application.Repositories uses Discount.Domain.Enums, so a change to Discount.Domain.Enums can break Discount.Application.Repositories, while a change to Discount.Application.Repositories can't break Discount.Domain.Enums.
Position
Below the diagonal: Discount.Application.Repositories uses a module listed above it, which is the healthy direction.
19β36 Inventory.Domain.Entities uses Inventory.Domain.Abstractionspart of a loop✕
Connections
6 pairs of types, where a type in Inventory.Domain.Entities uses a type in Inventory.Domain.Abstractions.
Inventory.Domain.Entities uses Inventory.Domain.Abstractions, so a change to Inventory.Domain.Abstractions can break Inventory.Domain.Entities, while a change to Inventory.Domain.Entities can't break Inventory.Domain.Abstractions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Notification.Application.Data.Repositories uses Notification.Domain.Enums, so a change to Notification.Domain.Enums can break Notification.Application.Data.Repositories, while a change to Notification.Application.Data.Repositories can't break Notification.Domain.Enums.
Position
Below the diagonal: Notification.Application.Data.Repositories uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Commands uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Order.Application.Features.Order.Commands, while a change to Order.Application.Features.Order.Commands can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Order.Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Commands uses Common.ValueObjects, so a change to Common.ValueObjects can break Order.Application.Features.Order.Commands, while a change to Order.Application.Features.Order.Commands can't break Common.ValueObjects.
Position
Below the diagonal: Order.Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Commands uses Order.Application.Dtos.Orders, so a change to Order.Application.Dtos.Orders can break Order.Application.Features.Order.Commands, while a change to Order.Application.Features.Order.Commands can't break Order.Application.Dtos.Orders.
Position
Below the diagonal: Order.Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Commands uses Order.Domain.Abstractions, so a change to Order.Domain.Abstractions can break Order.Application.Features.Order.Commands, while a change to Order.Application.Features.Order.Commands can't break Order.Domain.Abstractions.
Position
Below the diagonal: Order.Application.Features.Order.Commands uses a module listed above it, which is the healthy direction.
Order.Domain.Entities uses Order.Domain.Abstractions, so a change to Order.Domain.Abstractions can break Order.Domain.Entities, while a change to Order.Domain.Entities can't break Order.Domain.Abstractions.
Position
Below the diagonal: Order.Domain.Entities uses a module listed above it, which is the healthy direction.
Search.Application.Repositories uses Common.Models, so a change to Common.Models can break Search.Application.Repositories, while a change to Search.Application.Repositories can't break Common.Models.
Position
Below the diagonal: Search.Application.Repositories uses a module listed above it, which is the healthy direction.
Catalog.Application.Features.Product.Commands uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Catalog.Application.Features.Product.Commands, while a change to Catalog.Application.Features.Product.Commands can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Catalog.Application.Features.Product.Commands uses a module listed above it, which is the healthy direction.
Catalog.Application.Features.Product.Commands uses Catalog.Domain.Entities, so a change to Catalog.Domain.Entities can break Catalog.Application.Features.Product.Commands, while a change to Catalog.Application.Features.Product.Commands can't break Catalog.Domain.Entities.
Position
Below the diagonal: Catalog.Application.Features.Product.Commands uses a module listed above it, which is the healthy direction.
Catalog.Application.Features.Product.Commands uses Common.Models, so a change to Common.Models can break Catalog.Application.Features.Product.Commands, while a change to Catalog.Application.Features.Product.Commands can't break Common.Models.
Position
Below the diagonal: Catalog.Application.Features.Product.Commands uses a module listed above it, which is the healthy direction.
Catalog.Application.Features.Product.Commands uses Common.ValueObjects, so a change to Common.ValueObjects can break Catalog.Application.Features.Product.Commands, while a change to Catalog.Application.Features.Product.Commands can't break Common.ValueObjects.
Position
Below the diagonal: Catalog.Application.Features.Product.Commands uses a module listed above it, which is the healthy direction.
Catalog.Application.Features.Product.Commands uses Catalog.Application.Dtos.Products, so a change to Catalog.Application.Dtos.Products can break Catalog.Application.Features.Product.Commands, while a change to Catalog.Application.Features.Product.Commands can't break Catalog.Application.Dtos.Products.
Position
Below the diagonal: Catalog.Application.Features.Product.Commands uses a module listed above it, which is the healthy direction.
Catalog.Application.Models.Results uses Common.Models, so a change to Common.Models can break Catalog.Application.Models.Results, while a change to Catalog.Application.Models.Results can't break Common.Models.
Position
Below the diagonal: Catalog.Application.Models.Results uses a module listed above it, which is the healthy direction.
Catalog.Application.Models.Results uses BuildingBlocks.Pagination, so a change to BuildingBlocks.Pagination can break Catalog.Application.Models.Results, while a change to Catalog.Application.Models.Results can't break BuildingBlocks.Pagination.
Position
Below the diagonal: Catalog.Application.Models.Results uses a module listed above it, which is the healthy direction.
Catalog.Application.Models.Results uses Catalog.Application.Dtos.Products, so a change to Catalog.Application.Dtos.Products can break Catalog.Application.Models.Results, while a change to Catalog.Application.Models.Results can't break Catalog.Application.Dtos.Products.
Position
Below the diagonal: Catalog.Application.Models.Results uses a module listed above it, which is the healthy direction.
Discount.Application.Features.Coupon.Commands uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Discount.Application.Features.Coupon.Commands, while a change to Discount.Application.Features.Coupon.Commands can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Discount.Application.Features.Coupon.Commands uses a module listed above it, which is the healthy direction.
Discount.Application.Features.Coupon.Commands uses Common.ValueObjects, so a change to Common.ValueObjects can break Discount.Application.Features.Coupon.Commands, while a change to Discount.Application.Features.Coupon.Commands can't break Common.ValueObjects.
Position
Below the diagonal: Discount.Application.Features.Coupon.Commands uses a module listed above it, which is the healthy direction.
Discount.Application.Features.Coupon.Commands uses Discount.Application.Dtos.Coupons, so a change to Discount.Application.Dtos.Coupons can break Discount.Application.Features.Coupon.Commands, while a change to Discount.Application.Features.Coupon.Commands can't break Discount.Application.Dtos.Coupons.
Position
Below the diagonal: Discount.Application.Features.Coupon.Commands uses a module listed above it, which is the healthy direction.
Discount.Application.Features.Coupon.Commands uses Discount.Application.Repositories, so a change to Discount.Application.Repositories can break Discount.Application.Features.Coupon.Commands, while a change to Discount.Application.Features.Coupon.Commands can't break Discount.Application.Repositories.
Position
Below the diagonal: Discount.Application.Features.Coupon.Commands uses a module listed above it, which is the healthy direction.
Inventory.Application.Models.Results uses Common.Models, so a change to Common.Models can break Inventory.Application.Models.Results, while a change to Inventory.Application.Models.Results can't break Common.Models.
Position
Below the diagonal: Inventory.Application.Models.Results uses a module listed above it, which is the healthy direction.
Inventory.Application.Models.Results uses BuildingBlocks.Pagination, so a change to BuildingBlocks.Pagination can break Inventory.Application.Models.Results, while a change to Inventory.Application.Models.Results can't break BuildingBlocks.Pagination.
Position
Below the diagonal: Inventory.Application.Models.Results uses a module listed above it, which is the healthy direction.
Inventory.Application.Services uses Common.Models.Reponses, so a change to Common.Models.Reponses can break Inventory.Application.Services, while a change to Inventory.Application.Services can't break Common.Models.Reponses.
Position
Below the diagonal: Inventory.Application.Services uses a module listed above it, which is the healthy direction.
Inventory.Domain.Repositories uses Common.Models, so a change to Common.Models can break Inventory.Domain.Repositories, while a change to Inventory.Domain.Repositories can't break Common.Models.
Position
Below the diagonal: Inventory.Domain.Repositories uses a module listed above it, which is the healthy direction.
Inventory.Domain.Repositories uses Inventory.Domain.Entities, so a change to Inventory.Domain.Entities can break Inventory.Domain.Repositories, while a change to Inventory.Domain.Repositories can't break Inventory.Domain.Entities.
Position
Below the diagonal: Inventory.Domain.Repositories uses a module listed above it, which is the healthy direction.
Notification.Application.Features.Delivery.Commands uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Notification.Application.Features.Delivery.Commands, while a change to Notification.Application.Features.Delivery.Commands can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Notification.Application.Features.Delivery.Commands uses a module listed above it, which is the healthy direction.
Notification.Application.Features.Delivery.Commands uses Common.ValueObjects, so a change to Common.ValueObjects can break Notification.Application.Features.Delivery.Commands, while a change to Notification.Application.Features.Delivery.Commands can't break Common.ValueObjects.
Position
Below the diagonal: Notification.Application.Features.Delivery.Commands uses a module listed above it, which is the healthy direction.
Notification.Application.Features.Delivery.Commands uses Notification.Application.Data.Repositories, so a change to Notification.Application.Data.Repositories can break Notification.Application.Features.Delivery.Commands, while a change to Notification.Application.Features.Delivery.Commands can't break Notification.Application.Data.Repositories.
Position
Below the diagonal: Notification.Application.Features.Delivery.Commands uses a module listed above it, which is the healthy direction.
Notification.Application.Features.Notification.Queries uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Notification.Application.Features.Notification.Queries, while a change to Notification.Application.Features.Notification.Queries can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Notification.Application.Features.Notification.Queries uses a module listed above it, which is the healthy direction.
Notification.Application.Features.Notification.Queries uses Common.Models, so a change to Common.Models can break Notification.Application.Features.Notification.Queries, while a change to Notification.Application.Features.Notification.Queries can't break Common.Models.
Position
Below the diagonal: Notification.Application.Features.Notification.Queries uses a module listed above it, which is the healthy direction.
Notification.Application.Features.Notification.Queries uses Common.ValueObjects, so a change to Common.ValueObjects can break Notification.Application.Features.Notification.Queries, while a change to Notification.Application.Features.Notification.Queries can't break Common.ValueObjects.
Position
Below the diagonal: Notification.Application.Features.Notification.Queries uses a module listed above it, which is the healthy direction.
Notification.Application.Features.Notification.Queries uses Notification.Application.Data.Repositories, so a change to Notification.Application.Data.Repositories can break Notification.Application.Features.Notification.Queries, while a change to Notification.Application.Features.Notification.Queries can't break Notification.Application.Data.Repositories.
Position
Below the diagonal: Notification.Application.Features.Notification.Queries uses a module listed above it, which is the healthy direction.
Order.Api.Endpoints uses Common.Models, so a change to Common.Models can break Order.Api.Endpoints, while a change to Order.Api.Endpoints can't break Common.Models.
Position
Below the diagonal: Order.Api.Endpoints uses a module listed above it, which is the healthy direction.
Order.Api.Endpoints uses Order.Application.Dtos.Orders, so a change to Order.Application.Dtos.Orders can break Order.Api.Endpoints, while a change to Order.Api.Endpoints can't break Order.Application.Dtos.Orders.
Position
Below the diagonal: Order.Api.Endpoints uses a module listed above it, which is the healthy direction.
Order.Api.Endpoints uses Common.Models.Reponses, so a change to Common.Models.Reponses can break Order.Api.Endpoints, while a change to Order.Api.Endpoints can't break Common.Models.Reponses.
Position
Below the diagonal: Order.Api.Endpoints uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Queries uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Order.Application.Features.Order.Queries, while a change to Order.Application.Features.Order.Queries can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Order.Application.Features.Order.Queries uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Queries uses Common.Models, so a change to Common.Models can break Order.Application.Features.Order.Queries, while a change to Order.Application.Features.Order.Queries can't break Common.Models.
Position
Below the diagonal: Order.Application.Features.Order.Queries uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Queries uses Common.ValueObjects, so a change to Common.ValueObjects can break Order.Application.Features.Order.Queries, while a change to Order.Application.Features.Order.Queries can't break Common.ValueObjects.
Position
Below the diagonal: Order.Application.Features.Order.Queries uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Queries uses Order.Domain.Abstractions, so a change to Order.Domain.Abstractions can break Order.Application.Features.Order.Queries, while a change to Order.Application.Features.Order.Queries can't break Order.Domain.Abstractions.
Position
Below the diagonal: Order.Application.Features.Order.Queries uses a module listed above it, which is the healthy direction.
Order.Application.Features.Order.Queries uses Order.Domain.Entities, so a change to Order.Domain.Entities can break Order.Application.Features.Order.Queries, while a change to Order.Application.Features.Order.Queries can't break Order.Domain.Entities.
Position
Below the diagonal: Order.Application.Features.Order.Queries uses a module listed above it, which is the healthy direction.
Catalog.Api.Endpoints uses Common.Models, so a change to Common.Models can break Catalog.Api.Endpoints, while a change to Catalog.Api.Endpoints can't break Common.Models.
Position
Below the diagonal: Catalog.Api.Endpoints uses a module listed above it, which is the healthy direction.
Catalog.Api.Endpoints uses Common.Models.Reponses, so a change to Common.Models.Reponses can break Catalog.Api.Endpoints, while a change to Catalog.Api.Endpoints can't break Common.Models.Reponses.
Position
Below the diagonal: Catalog.Api.Endpoints uses a module listed above it, which is the healthy direction.
Catalog.Api.Endpoints uses Catalog.Application.Models.Results, so a change to Catalog.Application.Models.Results can break Catalog.Api.Endpoints, while a change to Catalog.Api.Endpoints can't break Catalog.Application.Models.Results.
Position
Below the diagonal: Catalog.Api.Endpoints uses a module listed above it, which is the healthy direction.
Inventory.Api.Endpoints uses Common.Models, so a change to Common.Models can break Inventory.Api.Endpoints, while a change to Inventory.Api.Endpoints can't break Common.Models.
Position
Below the diagonal: Inventory.Api.Endpoints uses a module listed above it, which is the healthy direction.
Inventory.Api.Endpoints uses Common.Models.Reponses, so a change to Common.Models.Reponses can break Inventory.Api.Endpoints, while a change to Inventory.Api.Endpoints can't break Common.Models.Reponses.
Position
Below the diagonal: Inventory.Api.Endpoints uses a module listed above it, which is the healthy direction.
Inventory.Api.Endpoints uses Inventory.Application.Models.Results, so a change to Inventory.Application.Models.Results can break Inventory.Api.Endpoints, while a change to Inventory.Api.Endpoints can't break Inventory.Application.Models.Results.
Position
Below the diagonal: Inventory.Api.Endpoints uses a module listed above it, which is the healthy direction.
Inventory.Domain.Abstractions uses Inventory.Domain.Repositories, so a change to Inventory.Domain.Repositories can break Inventory.Domain.Abstractions, while a change to Inventory.Domain.Abstractions can't break Inventory.Domain.Repositories.
Position
Below the diagonal: Inventory.Domain.Abstractions uses a module listed above it, which is the healthy direction.
Inventory.Infrastructure.Services uses Common.Models.Reponses, so a change to Common.Models.Reponses can break Inventory.Infrastructure.Services, while a change to Inventory.Infrastructure.Services can't break Common.Models.Reponses.
Position
Below the diagonal: Inventory.Infrastructure.Services uses a module listed above it, which is the healthy direction.
Inventory.Infrastructure.Services uses Inventory.Application.Services, so a change to Inventory.Application.Services can break Inventory.Infrastructure.Services, while a change to Inventory.Infrastructure.Services can't break Inventory.Application.Services.
Position
Below the diagonal: Inventory.Infrastructure.Services uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Commands uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Inventory.Application.Features.InventoryItem.Commands, while a change to Inventory.Application.Features.InventoryItem.Commands can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Commands uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Commands uses Common.ValueObjects, so a change to Common.ValueObjects can break Inventory.Application.Features.InventoryItem.Commands, while a change to Inventory.Application.Features.InventoryItem.Commands can't break Common.ValueObjects.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Commands uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Commands uses Inventory.Application.Services, so a change to Inventory.Application.Services can break Inventory.Application.Features.InventoryItem.Commands, while a change to Inventory.Application.Features.InventoryItem.Commands can't break Inventory.Application.Services.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Commands uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Commands uses Inventory.Domain.Abstractions, so a change to Inventory.Domain.Abstractions can break Inventory.Application.Features.InventoryItem.Commands, while a change to Inventory.Application.Features.InventoryItem.Commands can't break Inventory.Domain.Abstractions.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Commands uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Queries uses BuildingBlocks.CQRS, so a change to BuildingBlocks.CQRS can break Inventory.Application.Features.InventoryItem.Queries, while a change to Inventory.Application.Features.InventoryItem.Queries can't break BuildingBlocks.CQRS.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Queries uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Queries uses Common.Models, so a change to Common.Models can break Inventory.Application.Features.InventoryItem.Queries, while a change to Inventory.Application.Features.InventoryItem.Queries can't break Common.Models.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Queries uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Queries uses Inventory.Application.Models.Results, so a change to Inventory.Application.Models.Results can break Inventory.Application.Features.InventoryItem.Queries, while a change to Inventory.Application.Features.InventoryItem.Queries can't break Inventory.Application.Models.Results.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Queries uses a module listed above it, which is the healthy direction.
Inventory.Application.Features.InventoryItem.Queries uses Inventory.Domain.Abstractions, so a change to Inventory.Domain.Abstractions can break Inventory.Application.Features.InventoryItem.Queries, while a change to Inventory.Application.Features.InventoryItem.Queries can't break Inventory.Domain.Abstractions.
Position
Below the diagonal: Inventory.Application.Features.InventoryItem.Queries uses a module listed above it, which is the healthy direction.
Inventory.Domain.Events uses Inventory.Domain.Entities, so a change to Inventory.Domain.Entities can break Inventory.Domain.Events, while a change to Inventory.Domain.Events can't break Inventory.Domain.Entities.
Position
Below the diagonal: Inventory.Domain.Events uses a module listed above it, which is the healthy direction.
Inventory.Domain.Events uses Inventory.Domain.Abstractions, so a change to Inventory.Domain.Abstractions can break Inventory.Domain.Events, while a change to Inventory.Domain.Events can't break Inventory.Domain.Abstractions.
Position
Below the diagonal: Inventory.Domain.Events uses a module listed above it, which is the healthy direction.
At a glance β Code Health Β· 43% Β· Weak Β· gated by D3, D18, R1, R7 Β·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 β Authentication Failures
331
High / Critical
A05:2025 β Injection
281
High / Critical
A03:2025 β Software Supply Chain Failures
101
High / Critical
A02:2025 β Security Misconfiguration
81
High / Critical
Roadmap
Top priorities: Resolve the 227 Leaked secret finding(s) in REDACTED Scanning β start with REDACTED (112), REDACTED (112), REDACTED (2); Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No tests found finding(s) in Test Distribution.
Ranked by impact Γ· effort. "Helps" is the estimated gain on the 0β100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No tests found finding(s) in Test Distribution.
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others β never process-wide.
Per-file score 0β10 β a quality signature. Of 442 files carrying findings, judged against the Production bar: 13% slop Β· 36% mixed Β· 51% near-clean.
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 β 775
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 β 893
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 β 395
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved β 7
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository β a backup job that nothing shows was ever restored from proves
nothing about restores β or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment β run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 117 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: β Measured β a deterministic fact (LoC, complexity, coverage); ~ Modeled β an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): β Tool-verified means the property itself was measured across the surface; β Nothing flagged means the probes came back clean β a claim bounded by what a repository can show; β Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence β absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked β 117 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, 1976 of 2063 do; the remainder are repo-wide signals β a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score β and this report, byte for byte β is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) β re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time β a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares npm dependencies as well as NuGet ones, and the counts on this row cover the NuGet side ONLY. This dimension did read 2 npm lockfile(s) and identified 378 package(s) to grade, but the npm registry could not be asked about all of them (registry returned 429), so the npm half ABSTAINS rather than report a partly-checked dependency set as a complete answer. Their absence from the counts above is unmeasured currency β not a finding that those dependencies are current.
D17 Explicit Debt β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 10 deducted marker(s) and the 0.7/KLoC density on this row were taken over this repository's .NET projects ALONE: .jsx (65,303 lines, 67% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED β its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
D19 Documentation Quality β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D19 Documentation Quality β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run β this says nothing about whether its names are consistent.
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.
D32 Data Compliance (PII/GDPR) β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. `src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs`, `src/JobOrchestrator/App.Job/Jobs/Inventory/ExpireInventoryReservationsJob.cs`, `src/JobOrchestrator/App.Job/Jobs/Report/SyncDashboardReportJob.cs`, `src/JobOrchestrator/App.Job/Quartz/QuartzHostedService.cs`, `src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs`, β¦ (+162 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported β a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AC2 Forms & labels β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 424 further occurrence(s) are not listed individually; the score already reflects all 464.
AC3 Page structure β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
AC4 Keyboard semantics β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
AC6 Visual & motion safety β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 34 further occurrence(s) are not listed individually; the score already reflects all 74.
AXR1 Runtime accessibility β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 β the compose project is invalid) β time="2026-11-09T02:33:53Z" level=warning msg="The \"PROMETHEUS_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-09T02:33:53Z" level=warning msg="The \"CADVISOR_IMAGE_NAME\" variable is not set. Defaulting to a blank string." service "rabbitmq" has neither an image nor a build context specified: invalid compose project; runtime evidence skipped.
DM12 Ambient inputs in the domain β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 53 further occurrence(s) are not listed individually; the score already reflects all 93.
DM8 Value-object opportunities β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
M4 Documentation accuracy β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P1 CI/CD gates β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched β so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
R10 Code Duplication β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 440 further occurrence(s) are not listed individually; the score already reflects all 480.
R7 Dead Code β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 186 further occurrence(s) are not listed individually; the score already reflects all 226.
X2 Cancellation propagation β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 60 further occurrence(s) are not listed individually; the score already reflects all 100.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared β every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap β a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see β the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically β it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type β a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module β one class/IIFE β earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity β an in-process token-stream comparison over sliding windows, with type-aware normalization β so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED β its repetition is the tool's, not the team's β so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies β runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic β it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image β the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles β a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree β a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy β mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history β a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension β pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts β leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project β a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural β it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns β a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) β it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases β a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules β it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen β a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally β the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup β a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively β flagged only when it carries NO label/aria-label/aria-labelledby/id/name β but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree β landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes β interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape β roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES β Vue v-if/v-else/v-show and Alpine x-if/x-show β so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction β literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${β¦}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only β an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics β a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention β a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C3 Audit Trail: This control is scored from in-repo evidence only β a working control configured outside the repository leaves no signal a static scan can credit.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body β a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain β infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see β only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
46 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was index.InventoryPage at 171. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Fileinput.Fileinput at 18 β they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason β every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Apps/App.Admin/src/components/ui/Fileinput.jsx (Fileinput.Fileinput at 18), src/Services/Catalog/Core/Catalog.Infrastructure/Data/ProductSeedData.cs (ProductSeedData.GetThumbnailUrl at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 37 more group(s) β more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity β start with index.InventoryPage (cyclomatic 171), index.CouponPage (cyclomatic 128). β This score is capped by its worst body, so a finding fixed alone moves it by almost nothing β the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.4 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Prevented β provenance only; does not change the score.
Detailed fixes: d1_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 42 more group(s) β more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity β start with index.InventoryPage (cognitive 163). β Refactoring it lifts Cognitive Complexity from 5.5 to about 5.8/10.
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 Classes0.0 / 10Criticalβ 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 141 FunctionTooLong finding(s) in God Classes β start with index.jsx (15), KeycloakContext.jsx (2), FarzaaContext.jsx. β One of this dimension's main actionable groups (141 warning-level).
Resolve the 15 FileTooLong finding(s) in God Classes β start with index.jsx (6), FarzaaContext.jsx, edit-product.jsx. β One of this dimension's main actionable groups (15 warning-level).
Resolve the 4 ClassTooLong finding(s) in God Classes β start with dropdown.jsx, typography.jsx, card.jsx. β One of this dimension's main actionable groups (4 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.
106 duplicated block group(s) detected. A further 13 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .jsx (67% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 67 more group(s) β more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (19 lines × 2) finding(s) in Code Duplication β start with MySqlDatabaseProvider.cs (2), OutboxRepository.cs, OutboxMessageEntity.cs. β One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (13 lines × 2) finding(s) in Code Duplication β start with CreateProductCommand.cs, AddressDto.cs, GetAllOrdersFilter.cs. β One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication β start with GetAllAvailableProductsQuery.cs, OutboxMessageEntity.cs, InventoryHistoryConfiguration.cs. β One of this dimension's main actionable groups (4 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Verified β provenance only; does not change the score.
Detailed fixes: d4_recommendation.md Β· top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 Β· Coupling9.9 / 10Stronggated by 1 serious findingβ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type β the population is all types, not a name convention.
Off the main sequence: EventSourcingsrc/Shared/EventSourcing/EventSourcing.csproj:1
Off the main sequence: Common Β· Γ2REDACTED:1
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling β start with EventSourcing.csproj. β One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Prevented β provenance only; does not change the score.
Detailed fixes: d5_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class β the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) β start with ProductEntity.cs. β One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Verified β provenance only; does not change the score.
Detailed fixes: d6_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable β never a LoC-ratio proxy folded in as if measured. Deterministic.
No automated tests β no test code was found in this repository.
No automated tests
What to do
Resolve the 1 No automated tests finding(s) in Code Coverage. β One of this dimension's main actionable groups (1 issue-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Verified β provenance only; does not change the score.
Detailed fixes: d8_recommendation.md Β· top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 Β· Test Distribution0.0 / 10Criticalβ 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.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
59 outdated, 3 vulnerable, 6 deprecated packages. NuGet only β this repository also declares npm dependencies, and the npm registry could not be asked about them here, so their currency is unmeasured rather than clean.
Resolve the 7 Deprecated finding(s) in Dependency Hygiene β start with REDACTED (6), package.json. β One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Outdated finding(s) in Dependency Hygiene β start with REDACTED (6). β One of this dimension's main actionable groups (6 recommendation-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Verified β provenance only; does not change the score.
Detailed fixes: d12_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 227 Leaked secret finding(s) in REDACTED Scanning β start with REDACTED (112), REDACTED (112), REDACTED (2). β One of this dimension's main actionable groups (227 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.
3 of 250 packages use a banned license. β DEPTH: this repository's MSBuild projects declare 65 direct `PackageReference`(s), and 185 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.
Resolve the 3 Banned license finding(s) in License Compliance β start with REDACTED (2). β One of this dimension's main actionable groups (3 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Verified β provenance only; does not change the score.
Detailed fixes: d14_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex β the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
D16 Β· Bus Factor10.0 / 10Exemplaryβ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
1 source file(s) have their living knowledge concentrated in one author (β₯90% of recent, decayed contribution). The largest is src/Services/Discount/Core/Discount.Infrastructure/Data/Extensions/DatabaseExtentions.cs. Counted over 117 of the 916 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Small-team knowledge concentration
β On the Gold path β maintain.
Detailed fixes: d16_recommendation.md Β· top locations in Appendix A, every location in findings.md.
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.
10 deducted debt markers + 62 dead symbols across 27172 LoC in the .NET projects (0.7/KLoC) β score 8.7. Measured on the .NET source only: .jsx (67% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
Dead code: PaginatedResult Β· Γ62src/Shared/BuildingBlocks/Pagination/PaginatedResult.cs:3
Whole file has no live code β 4 debt markers inside it Β· Γ2src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:24
+ 1 more group(s) β more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt β start with UnitOfWork.cs. β One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt β start with Directory.Build.props. β One of this dimension's main actionable groups (1 issue-level).
Resolve the 62 Dead code finding(s) in Explicit Debt β start with ApplicationMarker.cs (8), OutboxMessageEntity.cs (4), HashExtension.cs (3). β One of this dimension's main actionable groups (62 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). β Hardens enforcement from Documented toward Prevented β provenance only; does not change the score.
Detailed fixes: d17_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: Whether the 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.
58 projects, 916 source files, 27172 hand-written lines of code (27172 production / 0 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 3529 generated (machine-written code β designer, scaffolded and tool-emitted files β excluded from quality), 150 inter-project edges.
Resolve the 5 Shell project finding(s) in Solution Shape β start with Catalog.Contract.csproj, Discount.Contract.csproj, Order.Contract.csproj. β One of this dimension's main actionable groups (5 recommendation-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: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
What it measures: Whether comments are worth it β explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names Β· Γ5src/Shared/BuildingBlocks/Validators/CustomValidators.cs:24
What to do
Resolve the 82 redundant comment finding(s) in Comment Value β start with REDACTED (25), index.jsx (5), CheckoutSection.jsx (4). β One of this dimension's main actionable groups (82 recommendation-level).
Detailed fixes: d24_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call β low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (β€400 methods) β not exhaustive.
97 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located β so a call's collaborators sit together and tracing stays easy. Baseline: medium β clean/modular boundaries expected.
Resolve the 2 Pass-through layer finding(s) in Navigability β start with DbTransactionAdapter.cs (2). β One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d27_recommendation.md Β· top locations in Appendix A, every location in findings.md.
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.
103 finding(s): 0 critical, 103 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation β they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 65 REDACTED finding(s) in Secrets (history) β start with REDACTED (40), REDACTED (16), REDACTED (6). β One of this dimension's main actionable groups (65 issue-level).
Resolve the 38 High secret finding(s) in Secrets (history) β start with REDACTED (22), REDACTED (10), REDACTED (3). β One of this dimension's main actionable groups (38 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).
281 finding(s): 0 critical, 256 high, 25 medium, 0 low. 228 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` β one pinning decision is charged once, not once per lens. semgrep hit a parse error in 167 file(s) β `src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs` (line 12), `src/JobOrchestrator/App.Job/Jobs/Inventory/ExpireInventoryReservationsJob.cs` (line 17, line 18, line 19), `src/JobOrchestrator/App.Job/Jobs/Report/SyncDashboardReportJob.cs` (line 25, line 26, line 27, β¦), `src/JobOrchestrator/App.Job/Quartz/QuartzHostedService.cs` (line 9), `src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs` (lines 114β117, line 118), β¦ (+162 more) β so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 167 of those file(s) β `src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs`, `src/JobOrchestrator/App.Job/Jobs/Inventory/ExpireInventoryReservationsJob.cs`, `src/JobOrchestrator/App.Job/Jobs/Report/SyncDashboardReportJob.cs`, `src/JobOrchestrator/App.Job/Quartz/QuartzHostedService.cs`, `src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs`, β¦ (+162 more) β the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (28). β One of this dimension's main actionable groups (28 issue-level).
Resolve the 19 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (8), REDACTED (2), REDACTED. β One of this dimension's main actionable groups (19 warning-level).
No action in Static Analysis (SAST) β all 228 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. β One of this dimension's main actionable groups (228 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares β Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 64 High CVE finding(s) in Dependency Vulnerabilities β start with REDACTED (36), REDACTED (15), REDACTED (5). β One of this dimension's main actionable groups (64 issue-level).
Resolve the 20 Medium CVE finding(s) in Dependency Vulnerabilities β start with REDACTED (11), REDACTED (3), REDACTED (2). β One of this dimension's main actionable groups (20 warning-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities β start with REDACTED (3), REDACTED, REDACTED. β One of this dimension's main actionable groups (5 issue-level).
Detailed fixes: d30_recommendation.md Β· top locations in Appendix A, every location in findings.md.
Resolve the 56 Medium IaC finding(s) in IaC & Container Security β start with REDACTED (56). β One of this dimension's main actionable groups (56 warning-level).
Resolve the 8 High IaC finding(s) in IaC & Container Security β start with REDACTED (3), REDACTED (3), REDACTED (2). β One of this dimension's main actionable groups (8 issue-level).
Resolve the 17 Low IaC finding(s) in IaC & Container Security β start with REDACTED (17). β One of this dimension's main actionable groups (17 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.
23 of 117 significant source file(s) are orphaned β their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Services/Catalog/Core/Catalog.Infrastructure/Data/ProductSeedData.cs. Counted over 117 of the 916 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness β start with ProductSeedData.cs. β One of this dimension's main actionable groups (1 issue-level).
Resolve the 22 Orphaned file finding(s) in Knowledge Freshness β start with Repository.cs (2), SyncDashboardReportJob.cs, OrderCreatedIntegrationEventHandler.cs. β One of this dimension's main actionable groups (22 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. β 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 the build pipeline provides supply-chain integrity β generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals β generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions β scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) β more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing β start with REDACTED, REDACTED. β One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact β 10; present without a contact β 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
A vulnerability-disclosure policy (.github/SECURITY.md) is published with a reporting contact.
β On the Gold path β maintain.
Detailed fixes: d37_recommendation.md.
Do you agree with this assessment?
D39 Β· IL Efficiency9.9 / 10Exemplaryβ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
11 of 2417 first-party methods have an oversized IL body.
IL efficiency: 11 authored method(s) exceed the IL budgetsrc/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17
β On the Gold path β maintain.
Detailed fixes: d39_recommendation.md Β· top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable β a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it β a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
β On the Gold path β maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS Β· M = Maturity Β· P = Readiness.
AC1 Β· Text alternatives7.7 / 10Strongβ Tool-verified
Other Β· Accessibility β Whether non-text content carries a text alternative β img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements β img, area, input[type=image], svg, video, object, embed, canvas β across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script β tagged-template (html`β¦`) UIs and hyperscript DOM factories β is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions β accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied β and capture that asset wherever the media enters the product (upload, import or generation). β src/Apps/App.Admin/src/components/ui/VideoPlayer.jsx:12
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt β alt="" if it's purely decorative. (×5) β src/Apps/App.Admin/src/pages/forms/file-input/DropZone.jsx:45, src/Apps/App.Admin/src/pages/product/productDetails.jsx:627, src/Apps/App.Admin/src/pages/product/productDetails.jsx:667, β¦
What to do
Add a text alternative β alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 Β· Forms & labels4.0 / 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.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×25) β src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:208, src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:235, src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:213, β¦
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×9) β src/Apps/App.Admin/src/components/partials/cart/index.jsx:93, src/Apps/App.Admin/src/components/partials/header/Tools/MonoChrome.jsx:8, src/Apps/App.Admin/src/components/partials/header/index.jsx:104, β¦
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) β src/Apps/App.Admin/src/components/partials/ecommerce/rangeSlider.jsx:19, src/Apps/App.Admin/src/components/partials/ecommerce/rangeSlider.jsx:25, src/Apps/App.Admin/src/components/partials/ecommerce/rangeSlider.jsx:51, β¦
This UI-library field component is named only by a placeholder β a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) β labelling each item leaves the set unnamed. (×2) β src/Apps/App.Admin/src/components/partials/header/Tools/SearchModal.jsx:89, src/Apps/App.Admin/src/components/partials/header/Tools/SearchModal.jsx:96
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.
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). β src/Apps/App.Admin/src/pages/product/productDetails.jsx:386
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one. (×39) β src/Apps/App.Admin/src/pages/product/productDetails.jsx:546, src/Apps/App.Store/src/components/banner/BannerSection10.jsx:60, src/Apps/App.Store/src/components/banner/BannerSection10.jsx:105, β¦
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other Β· Accessibility β Whether interactive behaviour is keyboard-reachable β no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) β a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population β there is nothing to judge β so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. β An interactive element declared in a tagged-template (html`β¦`) or hyperscript frontend is NOT in this population β no producer reads either β so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×33) β src/Apps/App.Admin/src/components/partials/cart/index.jsx:93, src/Apps/App.Admin/src/components/partials/header/Tools/MonoChrome.jsx:8, src/Apps/App.Admin/src/components/partials/header/Tools/Notification.jsx:174, β¦
This <div> binds mouse-enter and mouse-leave and nothing else β no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. β src/Apps/App.Admin/src/components/partials/sidebar/index.jsx:38
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×2) β src/Apps/App.Admin/src/pages/app/chat/Chat.jsx:59, src/Apps/App.Admin/src/pages/app/chat/Chat.jsx:102
This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. (×2) β src/Apps/App.Store/src/components/accordion/FaqAccordionSection.jsx:22, src/Apps/App.Store/src/components/accordion/FaqAccordionSection.jsx:48
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. β src/Apps/App.Store/src/components/blog/BlogTagFilter.jsx:13
This <i> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. β src/Apps/App.Store/src/components/mobile-menu/MobileMenuSection.jsx:20
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other Β· Accessibility β Whether ARIA is used correctly β valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script β tagged-template (html`β¦`) UIs and hyperscript DOM factories β is not read at all.
Other Β· Accessibility β Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast β PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL β only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) β computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script β tagged-template (html`β¦`) UIs and hyperscript DOM factories β is not read at all.
<div> moves β its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant β and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. β src/Apps/App.Admin/src/components/Loader-circle.jsx:7
<svg> moves β its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant β and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×4) β src/Apps/App.Admin/src/components/Loading.jsx:16, src/Apps/App.Admin/src/components/ui/Button.jsx:55, src/Apps/App.Admin/src/components/ui/Button.jsx:116, β¦
This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×13) β src/Apps/App.Admin/src/components/partials/ecommerce/steps/cart-step.jsx:105, src/Apps/App.Admin/src/components/partials/footer/MobileFooter.jsx:18, src/Apps/App.Admin/src/components/partials/footer/MobileFooter.jsx:63, β¦
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). β src/Apps/App.Admin/src/pages/app/chat/Chat.jsx:204
The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. (×3) β src/Apps/App.Store/src/components/product/ProductDetailTextSection.jsx:72, src/Apps/App.Store/src/components/product/ProductDetailTextSection.jsx:105, src/Apps/App.Store/src/components/shop/ProductContainer.jsx:50
`&:hover` sets color: #ffffff on background-color: #FF7C7C β 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. β src/Apps/App.Store/public/assets/scss/sections/_category.scss:1107
`span` sets color: #fff on background-color: #FFA239 β 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. β src/Apps/App.Store/public/assets/scss/sections/_featured-products.scss:1566
`&.active` sets color: #fff on background-color: #B8860B β 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. β src/Apps/App.Store/public/assets/scss/pages/_shop.scss:275
`.fz-11-feature .fz-11-feature-tab1 li button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. β src/Apps/App.Store/public/assets/scss/sections/_featured-products.scss:2069
`.fz-11-feature .fz-11-feature-tab button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. β src/Apps/App.Store/public/assets/scss/sections/_featured-products.scss:2091
`input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. β src/Apps/App.Store/public/assets/scss/main/_global.scss:189
`.wrapper .rv-container input[type="range"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. β src/Apps/App.Store/public/assets/scss/main/_utils.scss:44
`.icon-line.line-tip` moves (`animation: icon-line-tip 0.75s`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:80
`.icon-line.line-long` moves (`animation: icon-line-long 0.75s`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:88
`.success-title` moves (`animation: fadeInUp 0.6s ease 0.3s backwards`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:175
`.success-message` moves (`animation: fadeInUp 0.6s ease 0.4s backwards`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:183
`.order-number` moves (`animation: fadeInUp 0.6s ease 0.5s backwards`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:191
`.success-note` moves (`animation: fadeInUp 0.6s ease 0.6s backwards`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:211
`.success-btn` moves (`animation: fadeInUp 0.6s ease 0.7s backwards`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:226
`.confetti` moves (`animation: confetti-fall 3s ease-out forwards`) 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. β src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:285
`.fz-3-banner-section .fz-3-banner-product-cards .fz-3-single-product` moves (`animation: upDown 2s linear infinite alternate`) 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. β src/Apps/App.Store/public/assets/scss/sections/_banner.scss:194
`.fz-2-banner-section .fz-banner-vid .fz-banner-rounded-sticker .fz-rotateText` moves (`animation: rotateText 6s linear infinite`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. β src/Apps/App.Store/public/assets/scss/sections/_banner.scss:540
`.fz-1-banner-section .fz-1-banner-img-container .sticker-container .sticker` moves (`animation: rotateText 6s linear infinite`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. β src/Apps/App.Store/public/assets/scss/sections/_banner.scss:793
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 584 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. β src/Apps/App.Store/package.json:37
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.
Other Β· Architecture β Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other Β· Architecture β Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The namespaces Inventory.Domain.Abstractions β Inventory.Domain.Entities β Inventory.Domain.Repositories depend on each other. The lightest dependency in the cycle is Inventory.Domain.Repositories β Inventory.Domain.Entities (Inventory.Domain.Repositories.IInboxMessageRepository β Inventory.Domain.Entities.InboxMessageEntity, 3 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. β src/Services/Inventory/Core/Inventory.Domain/Repositories/IInboxMessageRepository.cs:3
The namespaces Order.Domain.Abstractions β Order.Domain.Entities β Order.Domain.Repositories depend on each other. The lightest dependency in the cycle is Order.Domain.Repositories β Order.Domain.Entities (Order.Domain.Repositories.IInboxMessageRepository β Order.Domain.Entities.InboxMessageEntity, 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. β src/Services/Order/Core/Order.Domain/Repositories/IInboxMessageRepository.cs:3
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 dependencies point inward (Domain β Application β Infrastructure/Web) β the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other Β· Architecture β Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other Β· Architecture β Whether interfaces stay focused rather than fat β the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count β members counted by name, so an overload group counts once β which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) β data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other Β· Architecture β Whether feature slices stay independent (no direct cross-slice references) β the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
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 Protection0.0 / 10Criticalβ Tool-verified
Other Β· Security β Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found β sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Other Β· Security β Whether access is authorized by default β a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
C3 Β· Audit Trail7.5 / 10Strongβ Tool-verified
Other Β· Security β Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit mechanism is present, but the trail is not yet complete β missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
Other Β· Domain Modelling β Whether aggregates reference each other by identity (id) rather than by direct object reference β the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set β a root not using those names is invisible.
Do you agree with this assessment?
DM10 Β· One transaction, one aggregate9.6 / 10Exemplaryβ Tool-verified
Other Β· Domain Modelling β Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one β the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type β three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
`CommitReservationCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. β src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/CommitReservationCommand.cs:34
`ExpireReservationCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. β src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ExpireReservationCommand.cs:31
`ReleaseReservationCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. β src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ReleaseReservationCommand.cs:39
`ReserveInventoryCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. β src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ReserveInventoryCommand.cs:53
What to do
Mutate one aggregate per operation and let the others follow from a domain event β the second aggregate reaching consistency a moment later is the design, not a compromise.
Other Β· Domain Modelling β Whether an aggregate can be constructed in a state its own rules forbid β a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
`InventoryItemEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Quantity`, `Reserved`, so `new InventoryItemEntity { Quantity = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs:14
`InventoryReservationEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Quantity`, so `new InventoryReservationEntity { Quantity = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs:12
`LocationEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Location`, so `new LocationEntity { Location = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs:9
`OrderItemEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Quantity`, so `new OrderItemEntity { Quantity = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Order/Core/Order.Domain/Entities/OrderItemEntity.cs:10
`CouponEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Code`, `Name`, `Description`, `Value`, β¦, so `new CouponEntity { Code = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:10
`DashboardTotalEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Bg`, `Text`, `Icon`, `Title`, β¦, so `new DashboardTotalEntity { Bg = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:9
`OrderGrowthLineChartEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Day`, `Value`, so `new OrderGrowthLineChartEntity { Day = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Report/Core/Report.Domain/Entities/OrderGrowthLineChartEntity.cs:9
`TopProductPieChartEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Name`, `Value`, so `new TopProductPieChartEntity { Name = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one. β src/Services/Report/Core/Report.Domain/Entities/TopProductPieChartEntity.cs:9
What to do
Give each aggregate one way in that can refuse β a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
Do you agree with this assessment?
DM12 Β· Ambient inputs in the domain8.6 / 10Strongβ Tool-verified
Other Β· Domain Modelling β Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly β an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads β DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp β resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
`BasketCheckoutDomainEventHandler` reads `DateTimeOffset.UtcNow` inside `PushToOutboxAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Basket/Core/Basket.Application/Features/Basket/EventHandlers/Domain/BasketCheckoutDomainEventHandler.cs:70
`BrandEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) β src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs:33, src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs:34
`BrandEntity` reads `DateTimeOffset.UtcNow` inside `Update`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs:49
`CategoryEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) β src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:41, src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:42
`CategoryEntity` reads `DateTimeOffset.UtcNow` inside `Update`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:61
`CouponEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:83, src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:85
`CouponEntity` reads `DateTimeOffset.UtcNow` inside `Update`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:110
`CouponEntity` reads `DateTimeOffset.UtcNow` inside `Approve`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:120
`CouponEntity` reads `DateTimeOffset.UtcNow` inside `Reject`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:130
`CouponEntity` reads `DateTimeOffset.UtcNow` inside `UpdateValidityPeriod`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:178
`CouponEntity` reads `DateTime.UtcNow` inside `IsValid`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:185, src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:186
`CouponEntity` reads `DateTime.UtcNow` inside `IsExpired`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:197
`DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) β src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:51, src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:52
`DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `UpdateCount`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:69
`DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `UpdateDisplay`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:78
`DeletedUnPublishedProductDomainEventHandler` reads `DateTimeOffset.UtcNow` inside `PushToOutboxAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/DeletedUnPublishedProductDomainEventHandler.cs:44
`DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) β src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:73, src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:74
`DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `UpdateStatus`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×3) β src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:82, src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:83, src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:84
`DeliveryEntity` draws from `Random.Shared` inside `RaiseError`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter β an injected `Random`, a seeded generator, or the already-chosen value β so a caller (and a test) can decide it. β src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:102
`IDomainEvent` reads `DateTime.Now` inside `OccurredOn`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×8) β src/Services/Catalog/Core/Catalog.Domain/Abstractions/IDomainEvent.cs:15, src/Services/Inventory/Core/Inventory.Domain/Abstractions/IDomainEvent.cs:15, src/Services/Order/Core/Order.Domain/Abstractions/IDomainEvent.cs:15, β¦
`InboxMessageEntity` draws from `Random.Shared` inside `RecordFailedAttempt`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter β an injected `Random`, a seeded generator, or the already-chosen value β so a caller (and a test) can decide it. β src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.cs:79
`InventoryHistoryEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryHistoryEntity.cs:21
`InventoryItemDeletedDomainEventHandler` reads `DateTimeOffset.UtcNow` inside `PushToOutboxAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/InventoryItemDeletedDomainEventHandler.cs:49
`InventoryItemEntity` reads `DateTimeOffset.UtcNow` inside `Update`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs:87
`InventoryItemEntity` reads `DateTimeOffset.UtcNow` inside `Decrease`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs:136
What to do
Take the instant and the randomness as inputs to the domain methods that need them β inject `TimeProvider` (BCL, .NET 8+) and a `Random`/seeded generator β so a test can choose both.
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.
`IDomainEvent.EventId` 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. (×8) β src/Services/Catalog/Core/Catalog.Domain/Abstractions/IDomainEvent.cs:13, src/Services/Inventory/Core/Inventory.Domain/Abstractions/IDomainEvent.cs:13, src/Services/Order/Core/Order.Domain/Abstractions/IDomainEvent.cs:13, β¦
`CategoryEntity.ParentId` 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. β src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:19
`ProductEntity.BrandId` 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. β src/Services/Catalog/Core/Catalog.Domain/Entities/ProductEntity.cs:50
`DeletedUnPublishedProductDomainEvent.ProductId` 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. β src/Services/Catalog/Core/Catalog.Domain/Events/DeletedUnPublishedProductDomainEvent.cs:9
`InventoryItemEntity.LocationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs:26
`InventoryReservationEntity.ReferenceId` 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. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs:18
`InventoryReservationEntity.LocationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs:26
`LocationChangedDomainEvent.InventoryItemId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/LocationChangedDomainEvent.cs:10
`LocationChangedDomainEvent.ProductId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/LocationChangedDomainEvent.cs:11
`ReservationCommittedDomainEvent.ReservationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:10
`ReservationCommittedDomainEvent.ProductId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:11
`ReservationCommittedDomainEvent.ReferenceId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:13
`ReservationCommittedDomainEvent.LocationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:14
`ReservationCreatedDomainEvent.ReservationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:10
`ReservationCreatedDomainEvent.ProductId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:11
`ReservationCreatedDomainEvent.ReferenceId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:13
`ReservationCreatedDomainEvent.LocationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:14
`ReservationExpiredDomainEvent.ReservationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:10
`ReservationExpiredDomainEvent.ProductId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:11
`ReservationExpiredDomainEvent.ReferenceId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:13
`ReservationExpiredDomainEvent.LocationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:14
`ReservationReleasedDomainEvent.ReservationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationReleasedDomainEvent.cs:10
`ReservationReleasedDomainEvent.ProductId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationReleasedDomainEvent.cs:11
`ReservationReleasedDomainEvent.ReferenceId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationReleasedDomainEvent.cs:13
`ReservationReleasedDomainEvent.LocationId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/ReservationReleasedDomainEvent.cs:14
`StockChangedDomainEvent.InventoryItemId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/StockChangedDomainEvent.cs:11
`StockChangedDomainEvent.ProductId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/StockChangedDomainEvent.cs:12
`TransferOutDomainEvent.ProductId` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/TransferOutDomainEvent.cs:11
`OrderItemEntity.OrderId` 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. β src/Services/Order/Core/Order.Domain/Entities/OrderItemEntity.cs:14
`ShoppingCartEntity.UserId` is a raw `String` β give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. β src/Services/Basket/Core/Basket.Domain/Entities/ShoppingCartEntity.cs:15
`DeliveryEntity.EventId` 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. β src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:14
`NotificationEntity.UserId` 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. β src/Services/Notification/Core/Notification.Domain/Entities/NotificationEntity.cs:15
`TemplateEntity.Key` 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. β src/Services/Notification/Core/Notification.Domain/Entities/TemplateEntity.cs:14
What to do
Adopt strongly-typed ids across the domain β finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Other Β· Domain Modelling β Whether cross-context integration events stay loosely coupled β no producer-owned enums/domain types leaking to consumers. Shared-kernel/contracts types are allowed.
Method: Roslyn (DDD-gated): integration-event properties scanned for producer-domain type/enum leaks versus primitives and shared-kernel types. Deterministic, hard fact.
Do you agree with this assessment?
DM4 Β· Rich vs anemic model10.0 / 10Exemplaryβ 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.
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.
`BrandEntity` exposes publicly writable state (Name, Slug). β src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs:9
`OrderGrowthLineChartEntity` exposes publicly writable state (Day, Value, Date). β src/Services/Report/Core/Report.Domain/Entities/OrderGrowthLineChartEntity.cs:9
`TopProductPieChartEntity` exposes publicly writable state (Name, Value). β src/Services/Report/Core/Report.Domain/Entities/TopProductPieChartEntity.cs:9
What to do
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Other Β· Domain Modelling β Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) β the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES β resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES β rename the layer and the check evaporates.
`Entity` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×4) β src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs:14, src/Services/Discount/Core/Discount.Domain/Abstractions/Entity.cs:14, src/Services/Notification/Core/Notification.Domain/Abstractions/Entity.cs:14, β¦
`Entity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×4) β src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs:15, src/Services/Discount/Core/Discount.Domain/Abstractions/Entity.cs:15, src/Services/Notification/Core/Notification.Domain/Abstractions/Entity.cs:15, β¦
`EntityId` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×2) β src/Services/Basket/Core/Basket.Domain/Abstractions/EntityId.cs:14, src/Services/Discount/Core/Discount.Domain/Abstractions/EntityId.cs:14
`EntityId` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. (×2) β src/Services/Basket/Core/Basket.Domain/Abstractions/EntityId.cs:15, src/Services/Discount/Core/Discount.Domain/Abstractions/EntityId.cs:15
`ShoppingCartItemEntity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. β src/Services/Basket/Core/Basket.Domain/Entities/ShoppingCartItemEntity.cs:14
`DeletedUnPublishedProductDomainEventHandler` (domain layer) names `IDocumentSession` from `Marten` β a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. β src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/DeletedUnPublishedProductDomainEventHandler.cs:16
`UpsertedProductDomainEventHandler` (domain layer) names `IDocumentSession` from `Marten` β a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. β src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/UpsertedProductDomainEventHandler.cs:16
`NotificationEntity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it. β src/Services/Notification/Core/Notification.Domain/Entities/NotificationEntity.cs:15
The domain project `Basket.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it. β src/Services/Basket/Core/Basket.Domain/Basket.Domain.csproj:5
The domain project `Discount.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it. β src/Services/Discount/Core/Discount.Domain/Discount.Domain.csproj:5
The domain project `Notification.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it. β src/Services/Notification/Core/Notification.Domain/Notification.Domain.csproj:5
The domain project `Report.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it. β src/Services/Report/Core/Report.Domain/Report.Domain.csproj:5
What to do
Invert domainβinfrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
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.
`InventoryHistoryRepository` is a repository over `InventoryHistoryEntity`, 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 `InventoryHistoryEntity` through its owning aggregate instead. β src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/InventoryHistoryRepository.cs:11
`LocationRepository` is a repository over `LocationEntity`, 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 `LocationEntity` through its owning aggregate instead. β src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/LocationRepository.cs:11
`IOrderItemRepository` is a repository over `OrderItemEntity`, 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 `OrderItemEntity` through its owning aggregate instead. β src/Services/Order/Core/Order.Domain/Repositories/IOrderItemRepository.cs:9
What to do
Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
Other Β· Domain Modelling β Whether one domain rule is decided β or one measurement produced β in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type β operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of β₯2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own β the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Inventory.Domain.Entities.InventoryReservationEntity's [ReferenceId, Status] are judged in Inventory.Application.Features.InventoryReservation.Commands.CommitReservationCommandHandler, Inventory.Application.Features.InventoryReservation.Commands.ReleaseReservationCommandHandler β 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.
Discount.Domain.Entities.CouponEntity's [MaxUsage, Status, UsageCount, ValidFrom, ValidTo] are judged in Discount.Infrastructure.Data.Extensions.DatabaseExtentions, Discount.Infrastructure.Repositories.CouponRepository β 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.
`UpsertedProductIntegrationEventHandler.Consume` makes a synchronous remote call (an HTTP call: `IKeycloakApi.GetAccessTokenAsync` is declared `[Post]`, a generated REST client via `IKeycloakService.GetUsersByRoleAsync`) while handling an event. The handler now depends, in real time, on another service being up and fast β the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. β src/Services/Notification/Worker/Notification.Worker.Consumer/EventHandlers/Integrations/UpsertedProductIntegrationEventHandler.cs:29
`OrderCreatedIntegrationEventHandler.Consume` makes a synchronous remote call (a gRPC call) while handling an event. The handler now depends, in real time, on another service being up and fast β the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. β src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCreatedIntegrationEventHandler.cs:30
What to do
Remove synchronous remote calls from message handlers β react by publishing further messages, so services stay temporally decoupled.
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.
`BasketCheckoutIntegrationEvent` 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. β src/Shared/EventSourcing/Events/Baskets/BasketCheckoutIntegrationEvent.cs:3
`TransferOutDomainEvent` 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. β src/Services/Inventory/Core/Inventory.Domain/Events/TransferOutDomainEvent.cs:9
`BasketCheckoutDomainEvent` 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. β src/Services/Basket/Core/Basket.Domain/Events/BasketCheckoutDomainEvent.cs:10
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.
Other Β· Readiness β Whether retry-prone mutations (command handlers and message or event consumers) are idempotent, so an at-least-once redelivery or a client retry does not apply the effect twice.
Method: Roslyn (any mutation, ungated): each persistent write of a command handler or message/event consumer is idempotent when a guard is visible (an exists/dedup read that gates an exit, upsert, idempotency-key/inbox used in a condition or store call, versioned or fixed-value write, dedup envelope or pipeline), at risk only on positive double-apply evidence (a fresh-identity insert, an accumulation on a loaded and saved object, a growing member list, an unkeyed POST/SMTP send/Stripe charge), and otherwise not classified. Deterministic, no model; not scored when more than half are not classified. Advisory.
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. Every mutation is classified exhaustively and deterministically: guarded, at risk on positive evidence, or not classified; the score is over the classified ones and is withheld when they are fewer than half.
`Commands.UpdateStockCommandHandler.Handle` mutates persistent state (a database save) and accumulates `Quantity += amount` (line 109) in `InventoryItemEntity.Increase`, so a re-run applies it again. A retry or at-least-once redelivery runs it again β add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. β src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/UpdateStockCommand.cs:49
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 Β· Code Health β Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other Β· Code Health β Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`PushToOutboxAsync` 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) β src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/DeletedUnPublishedProductDomainEventHandler.cs:32, src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/UpsertedProductDomainEventHandler.cs:32
`UseInfrastructure` looks like it should compute a result but its body just returns a constant β a placeholder return that was never filled in. β src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:52
A line of code has been commented out rather than removed β dead weight that rots and confuses. Delete it (version control remembers). (×37) β src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:47, src/Services/Catalog/Core/Catalog.Infrastructure/Repositories/OutboxRepository.cs:50, src/Services/Catalog/Core/Catalog.Infrastructure/Repositories/OutboxRepository.cs:96, β¦
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) β they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity Β· Maturity β Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a README to the 58 of 58 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.
Only 8/58 projects share a common root namespace β the code's module identity is inconsistent.
What to do
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) β the separation follows from putting the first tests in the right place.
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 project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 Β· CI/CD gates8.5 / 10Strongβ Tool-verified
Readiness Β· Readiness β Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
Only 38/45 service-like projects use logging (pure contract/DTO projects are excluded β they have nothing to log). Of those 45, 15 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead β an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object β rather than taking a logging dependency on your consumers' behalf.
Readiness Β· Readiness β Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step β in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 77652 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen β if that is your case the row is wrong, and saying so is more useful than adding a second scanner. β REDACTED:4
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices β including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. β REDACTED:9
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package β or `semgrep --config=auto`, which runs on any language β so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness Β· Readiness β Whether 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
The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read β confirm the gate is enforced before production promotion.
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.
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.
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 asynchronous code stays responsive β it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere β .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect β and, for a .NET library with β₯5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
5 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) β these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes β it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×4) β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16, src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:80, src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16, β¦
`.Wait()` blocks this thread until the async work completes β it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). β src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:78
What to do
Make the call chain async end-to-end and await it β never block on a Task with .Wait()/.GetAwaiter().GetResult().
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 · 648 plain JS β the untyped files are src/Apps/App.Admin/src/App.jsx, src/Apps/App.Admin/src/api/axiosInstance.js, src/Apps/App.Admin/src/api/endpoints.js, src/Apps/App.Admin/src/api/index.js, src/Apps/App.Admin/src/components/Loader-circle.jsx, src/Apps/App.Admin/src/components/Loading.jsx (+642 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.
99 duplicated blocks under src/Apps/App.Store/src/components/ have copies in at least two of the sibling directories authentication, banner, blog, brands, cart, category (+24 more sibling(s) not listed) β 49 of them are reported below, and 50 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 99 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 99 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 99 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. β src/Apps/App.Store/src/components/collection/CollectionSection.jsx:78
91 duplicated blocks under src/Apps/App.Admin/src/pages/ have copies in at least two of the sibling directories app, auth, brand, category, chart, components (+11 more sibling(s) not listed) β 63 of them are reported below, and 28 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 91 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 91 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 91 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. β src/Apps/App.Admin/src/pages/brand/index.jsx:274
42 duplicated blocks under src/Apps/ have copies in at least two of the sibling directories App.Admin, App.Store β 19 of them are reported below, and 23 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 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 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. β src/Apps/App.Admin/src/api/axiosInstance.js:1
34 duplicated blocks under src/Apps/App.Admin/src/pages/app/ have copies in at least two of the sibling directories calendar, chat, email, kanban, projects, todo β 21 of them are reported below, and 13 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 34 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 34 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 34 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. β src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:1
31 duplicated blocks under src/Apps/App.Admin/src/ have copies in at least two of the sibling directories components, constant, pages β 19 of them are reported below, and 12 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 31 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 31 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 31 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. β src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:195
src/Apps/App.Admin/src/pages/product/create-product.jsx:1 · src/Apps/App.Admin/src/pages/product/edit-product.jsx:1 β these 2 files are line-for-line copies of one another β 466 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/pages/product/create-product.jsx:1
src/Apps/App.Admin/src/pages/orders/create.jsx:1 · src/Apps/App.Admin/src/pages/orders/edit.jsx:1 β these 2 files are line-for-line copies of one another β 306 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/pages/orders/create.jsx:1
src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:66 · src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:52 β the two spans are one implementation copied and then locally edited β 1514 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. β src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:66
src/Apps/App.Admin/src/pages/forms/form-wizard/HorizentalWizard.jsx:1 · src/Apps/App.Admin/src/pages/forms/form-wizard/Vertical.jsx:1 β these 2 files are line-for-line copies of one another β 209 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/pages/forms/form-wizard/HorizentalWizard.jsx:1
src/Apps/App.Store/src/components/product/GlassSection-2.jsx:1 · src/Apps/App.Store/src/components/product/GlassSection.jsx:1 β these 2 files are line-for-line copies of one another β 207 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Store/src/components/product/GlassSection-2.jsx:1
src/Apps/App.Admin/src/api/axiosInstance.js:1 · src/Apps/App.Store/src/api/axiosInstance.js:1 β these 2 files are line-for-line copies of one another β 204 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/api/axiosInstance.js:1
src/Apps/App.Admin/src/services/keycloakService.js:29 · src/Apps/App.Store/src/services/keycloakService.js:41 β the two spans are one implementation copied and then locally edited β 1183 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. β src/Apps/App.Admin/src/services/keycloakService.js:29
src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:1 · src/Apps/App.Admin/src/pages/app/projects/AddProject.jsx:1 β these 2 files are line-for-line copies of one another β 178 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:1
src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:1 · src/Apps/App.Admin/src/pages/app/projects/EditProject.jsx:1 β these 2 files are line-for-line copies of one another β 171 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:1
src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:2 · src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:2 β these 2 files are line-for-line copies of one another β 155 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:2
src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:2 · src/Apps/App.Admin/src/pages/app/projects/AddProject.jsx:2 β these 2 files are line-for-line copies of one another β 154 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:2
src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:8 · src/Apps/App.Store/src/contexts/KeycloakContext.jsx:5 β the two spans are one implementation copied and then locally edited β 850 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. β src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:8
src/Apps/App.Admin/src/pages/product/index.jsx:186 · src/Apps/App.Admin/src/pages/product/orders.jsx:205 β the two spans are one implementation copied and then locally edited β 714 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. β src/Apps/App.Admin/src/pages/product/index.jsx:186
src/Apps/App.Admin/src/pages/brand/index.jsx:274 · src/Apps/App.Admin/src/pages/category/index.jsx:344 β 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. β src/Apps/App.Admin/src/pages/brand/index.jsx:274
src/Apps/App.Admin/src/pages/app/email/index.jsx:29 · src/Apps/App.Admin/src/pages/app/todo/index.jsx:75 β the two spans are one implementation copied and then locally edited β 613 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. β src/Apps/App.Admin/src/pages/app/email/index.jsx:29
src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:91 · src/Apps/App.Admin/src/components/partials/Table/team-table.jsx:198 β 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. β src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:91
src/Apps/App.Admin/src/pages/inventory/index.jsx:1505 · src/Apps/App.Admin/src/pages/inventory/index.jsx:1701 β 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. β src/Apps/App.Admin/src/pages/inventory/index.jsx:1505
src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:16 · src/Apps/App.Admin/src/pages/utility/invoice.jsx:71 β 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. β src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:16
src/Apps/App.Admin/src/pages/app/projects/project-details.jsx:118 · src/Apps/App.Admin/src/pages/dashboard/project.jsx:50 β 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. β src/Apps/App.Admin/src/pages/app/projects/project-details.jsx:118
src/Apps/App.Admin/src/components/partials/widget/chart/account-payable.jsx:5 · src/Apps/App.Admin/src/components/partials/widget/chart/account-receivable.jsx:5 β 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. β src/Apps/App.Admin/src/components/partials/widget/chart/account-payable.jsx:5
src/Apps/App.Admin/src/pages/inventory/index.jsx:1411 · src/Apps/App.Admin/src/pages/inventory/index.jsx:1607 β 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. β src/Apps/App.Admin/src/pages/inventory/index.jsx:1411
src/Apps/App.Admin/src/pages/coupon/index.jsx:675 · src/Apps/App.Admin/src/pages/orders/index.jsx:685 · src/Apps/App.Admin/src/pages/product/index.jsx:526 · src/Apps/App.Admin/src/pages/product/orders.jsx:478 β the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block β it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead β the whole function, component or branch these lines sit in β and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. β src/Apps/App.Admin/src/pages/coupon/index.jsx:675
src/Apps/App.Admin/src/pages/app/projects/ProjectList.jsx:247 · src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:310 · src/Apps/App.Admin/src/pages/utility/invoice.jsx:343 β 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. β src/Apps/App.Admin/src/pages/app/projects/ProjectList.jsx:247
src/Apps/App.Store/src/context/FarzaaContext.jsx:821 · src/Apps/App.Store/src/context/FarzaaContext.jsx:972 β the two spans are one implementation copied and then locally edited β 437 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters β or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. β src/Apps/App.Store/src/context/FarzaaContext.jsx:821
src/Apps/App.Admin/src/components/ui/InputGroup.jsx:34 · src/Apps/App.Admin/src/components/ui/Textinput.jsx:32 β the two spans are one implementation copied and then locally edited β 363 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. β src/Apps/App.Admin/src/components/ui/InputGroup.jsx:34
src/Apps/App.Admin/src/pages/notification/index.jsx:399 · src/Apps/App.Admin/src/pages/orders/index.jsx:685 · src/Apps/App.Admin/src/pages/product/index.jsx:526 · src/Apps/App.Admin/src/pages/product/orders.jsx:478 β the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block β it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead β the whole function, component or branch these lines sit in β and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. β src/Apps/App.Admin/src/pages/notification/index.jsx:399
src/Apps/App.Admin/src/pages/orders/details.jsx:532 · src/Apps/App.Admin/src/pages/orders/index.jsx:778 β 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. β src/Apps/App.Admin/src/pages/orders/details.jsx:532
src/Apps/App.Store/src/components/header/HeaderSection7.jsx:33 · src/Apps/App.Store/src/components/header/HeaderSection8.jsx:84 β the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. β src/Apps/App.Store/src/components/header/HeaderSection7.jsx:33
src/Apps/App.Admin/src/pages/product/orders.jsx:413 · src/Apps/App.Admin/src/pages/table/react-tables/ExampleTwo.jsx:219 β 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. β src/Apps/App.Admin/src/pages/product/orders.jsx:413
src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:159 · src/Apps/App.Admin/src/pages/table/react-tables/ExampleTwo.jsx:133 β 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. β src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:159
src/Apps/App.Admin/src/components/partials/Table/team-table.jsx:248 · src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:199 β the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. β src/Apps/App.Admin/src/components/partials/Table/team-table.jsx:248
src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:195 · src/Apps/App.Admin/src/pages/utility/invoice.jsx:284 β 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. β src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:195
src/Apps/App.Store/src/components/sliders/CupCakeSlider.jsx:1 · src/Apps/App.Store/src/components/sliders/LayerCakeSlider.jsx:1 · src/Apps/App.Store/src/components/sliders/PoundCakeSlider.jsx:1 β these 3 files are line-for-line copies of one another β 74 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. β src/Apps/App.Store/src/components/sliders/CupCakeSlider.jsx:1
src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:178 · src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:184 β the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. β src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:178
src/Apps/App.Admin/src/pages/coupon/index.jsx:588 · src/Apps/App.Admin/src/pages/product/index.jsx:439 β 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. β src/Apps/App.Admin/src/pages/coupon/index.jsx:588
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 Β· Architecture β Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
src/Apps/App.Admin/src/components/ui/InputGroup.jsx:4 imports cleave.js/dist/addons/cleave-phone.us, reaching past a declared dependency's public entry into its build output β that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. β src/Apps/App.Admin/src/components/ui/InputGroup.jsx:4
src/Apps/App.Admin/src/components/ui/Textinput.jsx:4 imports cleave.js/dist/addons/cleave-phone.us, reaching past a declared dependency's public entry into its build output β that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. β src/Apps/App.Admin/src/components/ui/Textinput.jsx:4
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
OrderDetails has cyclomatic complexity 63 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/orders/details.jsx:63
InventoryPage has cyclomatic complexity 48 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/inventory/index.jsx:53
(anonymous) has cyclomatic complexity 47 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:163
ProductDetails has cyclomatic complexity 44 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/product/productDetails.jsx:35
InputGroup has cyclomatic complexity 41 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/components/ui/InputGroup.jsx:6
CouponPage has cyclomatic complexity 40 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/coupon/index.jsx:36
Button has cyclomatic complexity 40 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/components/ui/Button.jsx:4
Modal has cyclomatic complexity 35 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/components/ui/Modal.jsx:5
getUserInfo has cyclomatic complexity 31 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side β extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) β src/Apps/App.Admin/src/services/keycloakService.js:266, src/Apps/App.Store/src/services/keycloakService.js:380
Textinput has cyclomatic complexity 29 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/components/ui/Textinput.jsx:5
CreateCoupon has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:15
fetchOrder has cyclomatic complexity 25 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/orders/edit.jsx:53
getInitialValues has cyclomatic complexity 24 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/product/edit-product.jsx:144
Ecommerce has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/product/index.jsx:43
OrderDetailModal has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Store/src/components/modal/OrderDetailModal.jsx:17
fetchProducts has cyclomatic complexity 23 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Store/src/context/FarzaaContext.jsx:244
onSubmit has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. β src/Apps/App.Admin/src/pages/product/create-product.jsx:136
syncUserInfo has cyclomatic complexity 20 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side β extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) β src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:68, src/Apps/App.Store/src/contexts/KeycloakContext.jsx:122
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic β€ 5.
Do you agree with this assessment?
R3 Β· Large Files8.1 / 10Strongβ 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.
src/Apps/App.Admin/src/pages/inventory/index.jsx has 1724 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/inventory/index.jsx:1
src/Apps/App.Store/src/context/FarzaaContext.jsx has 1102 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Store/src/context/FarzaaContext.jsx:1
src/Apps/App.Admin/src/pages/coupon/index.jsx has 1034 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/coupon/index.jsx:1
src/Apps/App.Admin/src/pages/orders/index.jsx has 865 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/orders/index.jsx:1
src/Apps/App.Admin/src/pages/category/index.jsx has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/category/index.jsx:1
src/Apps/App.Admin/src/constant/data.js has 717 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/constant/data.js:1
src/Apps/App.Admin/src/pages/product/index.jsx has 707 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/product/index.jsx:1
src/Apps/App.Admin/src/pages/product/edit-product.jsx has 701 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/product/edit-product.jsx:1
src/Apps/App.Admin/src/pages/product/productDetails.jsx has 677 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/product/productDetails.jsx:1
src/Apps/App.Admin/src/pages/product/create-product.jsx has 643 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/product/create-product.jsx:1
src/Apps/App.Admin/src/pages/brand/index.jsx has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/brand/index.jsx:1
src/Apps/App.Admin/src/pages/orders/details.jsx has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/orders/details.jsx:1
src/Apps/App.Admin/src/pages/components/modal.jsx has 604 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/components/modal.jsx:1
src/Apps/App.Admin/src/pages/product/orders.jsx has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/product/orders.jsx:1
src/Apps/App.Admin/src/constant/appex-chart.js has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/constant/appex-chart.js:1
src/Apps/App.Admin/src/pages/components/card.jsx has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/components/card.jsx:1
src/Apps/App.Admin/src/pages/components/dropdown.jsx has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/components/dropdown.jsx:1
src/Apps/App.Admin/src/pages/components/typography.jsx has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/components/typography.jsx:1
src/Apps/App.Admin/src/pages/components/colors.jsx has 478 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/components/colors.jsx:1
src/Apps/App.Admin/src/pages/orders/edit.jsx has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/orders/edit.jsx:1
src/Apps/App.Admin/src/pages/product/add-product.jsx has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/product/add-product.jsx:1
src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:1
src/Apps/App.Admin/src/pages/notification/index.jsx has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/notification/index.jsx:1
src/Apps/App.Admin/src/pages/orders/create.jsx has 430 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/orders/create.jsx:1
src/Apps/App.Store/src/services/keycloakService.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Store/src/services/keycloakService.js:1
src/Apps/App.Admin/src/pages/product/orderDetails.jsx has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/product/orderDetails.jsx:1
src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:1
src/Apps/App.Admin/src/pages/utility/invoice.jsx has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module. β src/Apps/App.Admin/src/pages/utility/invoice.jsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 Β· Test Coverage0.0 / 10Criticalβ 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.
0% of 644 production file(s) reachable from 0 test file(s) via the import graph β 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
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.
65 outdated package(s); JS/npm CVEs scored in D30
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 Β· Tooling10.0 / 10Exemplaryβ Tool-verified
React / JS Β· Readiness β Whether the project wires up test, lint and typecheck β detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 Β· Dead Code2.3 / 10Criticalβ 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 15 application, 4 tooling and 0 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 (15 application, 4 tooling, 0 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 (×21) β src/Apps/App.Admin/src/pages/components/modal.jsx, src/Apps/App.Admin/src/constant/appex-chart.js, src/Apps/App.Admin/src/pages/components/card.jsx, β¦
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/table/react-table.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Apps/App.Admin/src/pages/dashboard/crm.jsx, src/Apps/App.Admin/src/pages/table/react-table.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/pages/table/react-tables/ExampleTwo.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/projects/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) β src/Apps/App.Admin/src/pages/app/projects/ProjectList.jsx, src/Apps/App.Admin/src/pages/app/projects/EditProject.jsx, src/Apps/App.Admin/src/pages/app/projects/AddProject.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Apps/App.Admin/src/pages/app/projects/project-details.jsx, src/Apps/App.Admin/src/pages/dashboard/project.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/components/partials/Table/team-table.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/forms/form-wizard/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) β src/Apps/App.Admin/src/pages/forms/form-wizard/HorizentalWizard.jsx, src/Apps/App.Admin/src/pages/forms/form-wizard/Vertical.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/chart/appex-chart/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/pages/chart/appex-chart/Candlestick.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/kanban/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) β src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx, src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/dashboard/banking.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/components/partials/Table/transactions.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Apps/App.Admin/src/pages/dashboard/banking.jsx, src/Apps/App.Admin/src/pages/widget/statistic-widget.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/components/partials/widget/chart/group-chart5.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/forms/select/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/pages/forms/select/Options.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/todo/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) β src/Apps/App.Admin/src/pages/app/todo/EditTodo.jsx, src/Apps/App.Admin/src/pages/app/todo/AddTodo.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/chat/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/pages/app/chat/Chat.jsx
no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/calendar/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it β src/Apps/App.Admin/src/pages/app/calendar/EventModal.jsx
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.
Declared in src/Apps/App.Admin/package.json but never imported anywhere in that package or its workspace members β no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
`ServerCertificateCustomValidationCallback` is assigned `DangerousAcceptAnyServerCertificateValidator`, so every TLS peer certificate is accepted β including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic β the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one β compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else β and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship. β src/Services/Inventory/Core/Inventory.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:29
`ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. β src/Shared/BuildingBlocks/Authentication/Extensions/AuthorizationExtension.cs:45
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. (×15) β src/ApiGateway/YarpApiGateway/Program.cs:11, src/Services/Basket/Api/Basket.Api/Program.cs:9, src/Services/Catalog/Api/Catalog.Api/Program.cs:9, β¦
No UseHttpsRedirection/UseHsts and no reverse-proxy signal β transport security is unverified at the app layer. (β2.0 on this card.)
This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×15) β src/ApiGateway/YarpApiGateway/Program.cs:11, src/Services/Basket/Api/Basket.Api/Program.cs:9, src/Services/Catalog/Api/Catalog.Api/Program.cs:9, β¦
What to do
Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others β never process-wide.
Re-enable token validation β `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
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.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) β only skip this if a reverse proxy demonstrably terminates TLS.
Other Β· Code Health β Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay β a public sync API you cannot break, or a process entry point that must not return until the work finishes β the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×5) β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16, src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:80, src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16, β¦
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.
`transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 29). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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. β src/Services/Inventory/Core/Inventory.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:29
`transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 35). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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. β src/Services/Inventory/Core/Inventory.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:35
`transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 26). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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. β src/Services/Order/Core/Order.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:26
`transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 31). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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. β src/Services/Order/Core/Order.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:31
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 297/392 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up β whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice β judge against your hosting model.
No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken. (×16) β src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateBrand.cs:31, src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateCategory.cs:31, src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs:41, β¦
No CancellationToken parameter β this work can't be stopped early once started. (×19) β src/Services/Catalog/Api/Catalog.Api/Endpoints/DeleteBrand.cs:28, src/Services/Catalog/Api/Catalog.Api/Endpoints/DeleteProduct.cs:32, REDACTED:28, β¦
No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken. (×4) β src/Services/Catalog/Api/Catalog.Grpc/Services/CatalogGrpcService.cs:16, src/Services/Catalog/Api/Catalog.Grpc/Services/CatalogGrpcService.cs:32, src/Services/Catalog/Api/Catalog.Grpc/Services/CatalogGrpcService.cs:54, β¦
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 21 rejects `location` and line 21 reports that rejection as `ArgumentNullException` β but the condition's own test `string.IsNullOrWhiteSpace(location)` is true of a value that is NOT null: it is satisfied by an EMPTY `location`, and on that path `location` 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 this 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` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. β src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs:21
The guard on line 42 rejects `location` and line 42 reports that rejection as `ArgumentNullException` β but the condition's own test `string.IsNullOrWhiteSpace(location)` is true of a value that is NOT null: it is satisfied by an EMPTY `location`, and on that path `location` 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 this 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` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. β src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs:42
The guard on line 24 rejects `name` and line 24 reports that rejection as `ArgumentNullException` β but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` 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 this 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` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. β src/Services/Inventory/Core/Inventory.Domain/ValueObjects/Product.cs:24
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. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other Β· Code Health β Whether the work a diagnostic log line costs is paid only when that line is wanted β C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence β a LINQ operator, a materialisation, `string.Join`, a serializer β with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engineβs own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/β¦), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` β outside any arrow or function passed as an argument, which the logger calls only when the level is on β with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 Β· Document value interpolated into markup unescaped3.5 / 10Weakβ Tool-verified
Other Β· Security β Whether text read out of the document being converted is escaped before it is written into generated markup β a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF β the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`item.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. β src/Apps/App.Admin/src/components/ui/Accordion.jsx:48
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other Β· Code Health β Whether a value the caller is invited to supply is the value the type actually uses β a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engineβs own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other Β· Code Health β Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed β a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it β and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engineβs own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 Β· Collection changed while being enumerated10.0 / 10Exemplaryβ Nothing flagged
Other Β· Code Health β Whether a `foreach` leaves the collection it is walking alone β a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/β¦) on the very expression the loop is enumerating. Two arms. ARM A β the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B β the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 Β· Index access outside its own emptiness guard10.0 / 10Exemplaryβ Nothing flagged
Other Β· Code Health β Whether a condition that tests a value for emptiness indexes that same value only where the test holds β an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty β a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 Β· Per-element action decided by a fixed element10.0 / 10Exemplaryβ Nothing flagged
Other Β· Code Health β Whether a decision taken once per element is taken ABOUT that element β a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`βs condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move β written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engineβs own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = β¦; β¦; β¦)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other Β· Code Health β Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 Β· Support guard that admits what it rejects10.0 / 10Exemplaryβ Nothing flagged
Other Β· Code Health β Whether a guard written as a NEGATED `||` says what its author meant β `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read β an identifier or member access, never an invocation, which is a predicate rather than a capability flag β and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 Β· Type resolved by simple name across every loaded assembly10.0 / 10Exemplaryβ Nothing flagged
Other Β· Code Health β Whether a plugin lookup names the type it means β searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call β a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chainβs own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other Β· Code Health β Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engineβs own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard libraryβs `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`β¦`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravelβs `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentryβs structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${β¦}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gemβs `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{β¦}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other Β· Code Health β Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~2.8 `!` suppressions per 1k syntax nodes β 420 suppression(s) across the 150754 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage β what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; β30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim β a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by β¦") and is never the strongest area however high its average.
Unscored β 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score β either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate β 25 observation(s) recorded Β· Advisory β this card reports evidence and never carries a score.
X7 Silent fallback defaults β 18 observation(s) recorded Β· Advisory β this card reports evidence and never carries a score.
Not evidenced β 4 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 (event-sourced storage β lifecycle is stream archival / event TTL, not row CASCADE) β absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights β Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary β absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup β not evidenced β repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene β not evidenced β no changelog, version stamp or semver release tag in the repo
Not included β 22 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.
AX8 Test isolation β no test/production split to check
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 15 β the compose project is invalid) β time="2026-11-09T02:33:53Z" level=warning msg="The \"PROMETHEUS_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-09T02:33:53Z" level=warning msg="The \"CADVISOR_IMAGE_NAME\" variable is not set. Defaulting to a blank string." service "rabbitmq" has neither an image nor a build context specified: invalid compose project; 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.
D10 Test Quality β No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability β No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk β which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite β found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D21 Naming Consistency β Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
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) β 167 file(s) were not parsed by semgrep β the PII/GDPR ruleset never ran over them
D40 Network Egress Confinement β No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement β No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement β No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life β Platform end-of-life not assessed β this repository declares no platform this pass reads
D7 Architectural Integrity β no checkable ADRs and no dependency cycles β architectural integrity not assessed
DM8 Value-object opportunities β not scored β the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ES1 Event Sourcing β not scored β this repository shows only 1 of the 3 signals this lens looks for (an event-store package (Marten/EventStore))
P12 CI test-gate honesty β Reported, not scored β and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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
PF2 Allocation hygiene β Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
SC1 Supply-chain hygiene β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
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.
AC4 Β· Keyboard semanticsΒ· Click handler on a non-interactive <div> Β· Γ27
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/cart/index.jsx:93β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/header/Tools/MonoChrome.jsx:8β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/header/Tools/Notification.jsx:174β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/header/Tools/Profile.jsx:76β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/header/Tools/SwitchDark.jsx:11β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/header/index.jsx:104β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/header/index.jsx:120β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/header/index.jsx:141β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/settings/index.jsx:66β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/sidebar/Logo.jsx:53β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/sidebar/Navmenu.jsx:104β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/partials/sidebar/Submenu.jsx:21β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/ui/Accordion.jsx:20β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/ui/Alert.jsx:30β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/ui/Alert.jsx:38β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/components/ui/Button.jsx:81β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/app/chat/Chat.jsx:102β A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/app/chat/Contacts.jsx:11β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/app/chat/MyProfile.jsx:69β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/app/chat/MyProfile.jsx:90β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/app/todo/TodoHeader.jsx:30β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/notification/index.jsx:182β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/notification/index.jsx:196β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/notification/index.jsx:212β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> src/Apps/App.Admin/src/pages/notification/index.jsx:233β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
+ 2 more in this group β see findings.md.
AC2 Β· Forms & labelsΒ· <button> with no accessible text Β· Γ25
<button> with no accessible text src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:208β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:235β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:213β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:240β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/cart/cart-item.jsx:30β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/cart/cart-item.jsx:41β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/cart/cart-item.jsx:50β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/counter-button.jsx:30β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/counter-button.jsx:42β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/product-box.jsx:50β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/product-box.jsx:55β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/product-box.jsx:61β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/product-box.jsx:67β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/product-list.jsx:38β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/product-list.jsx:44β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/product-list.jsx:50β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/steps/cart-step.jsx:81β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/steps/cart-step.jsx:92β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/ecommerce/steps/cart-step.jsx:105β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/sidebar/MobileMenu.jsx:58β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/widget/task-list.jsx:98β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/partials/widget/task-list.jsx:102β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/ui/Modal.jsx:91β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/ui/Modal.jsx:156β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text src/Apps/App.Admin/src/components/ui/Pagination.jsx:33β A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
Domain depends on infrastructure: Entity src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs:14β `Entity` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Entity src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs:15β `Entity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: EntityId src/Services/Basket/Core/Basket.Domain/Abstractions/EntityId.cs:14β `EntityId` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: EntityId src/Services/Basket/Core/Basket.Domain/Abstractions/EntityId.cs:15β `EntityId` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ShoppingCartItemEntity src/Services/Basket/Core/Basket.Domain/Entities/ShoppingCartItemEntity.cs:14β `ShoppingCartItemEntity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: DeletedUnPublishedProductDomainEventHandler src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/DeletedUnPublishedProductDomainEventHandler.cs:16β `DeletedUnPublishedProductDomainEventHandler` (domain layer) names `IDocumentSession` from `Marten` β a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: UpsertedProductDomainEventHandler src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/UpsertedProductDomainEventHandler.cs:16β `UpsertedProductDomainEventHandler` (domain layer) names `IDocumentSession` from `Marten` β a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Entity src/Services/Discount/Core/Discount.Domain/Abstractions/Entity.cs:14β `Entity` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Entity src/Services/Discount/Core/Discount.Domain/Abstractions/Entity.cs:15β `Entity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: EntityId src/Services/Discount/Core/Discount.Domain/Abstractions/EntityId.cs:14β `EntityId` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: EntityId src/Services/Discount/Core/Discount.Domain/Abstractions/EntityId.cs:15β `EntityId` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Entity src/Services/Notification/Core/Notification.Domain/Abstractions/Entity.cs:14β `Entity` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Entity src/Services/Notification/Core/Notification.Domain/Abstractions/Entity.cs:15β `Entity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: NotificationEntity src/Services/Notification/Core/Notification.Domain/Entities/NotificationEntity.cs:15β `NotificationEntity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Entity src/Services/Report/Core/Report.Domain/Abstractions/Entity.cs:14β `Entity` (domain layer) names `BsonIdAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Entity src/Services/Report/Core/Report.Domain/Abstractions/Entity.cs:15β `Entity` (domain layer) names `BsonRepresentationAttribute` from `MongoDB.Bson.Serialization.Attributes` β a persistence type (as an attribute). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: Basket.Domain src/Services/Basket/Core/Basket.Domain/Basket.Domain.csproj:5β The domain project `Basket.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it.
Domain depends on infrastructure: Discount.Domain src/Services/Discount/Core/Discount.Domain/Discount.Domain.csproj:5β The domain project `Discount.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it.
Domain depends on infrastructure: Notification.Domain src/Services/Notification/Core/Notification.Domain/Notification.Domain.csproj:5β The domain project `Notification.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it.
Domain depends on infrastructure: Report.Domain src/Services/Report/Core/Report.Domain/Report.Domain.csproj:5β The domain project `Report.Domain` references `MongoDB.Bson` β a persistence dependency; the domain should own a port and let an infrastructure project reference it.
AC2 Β· Forms & labelsΒ· Custom control with no accessible name on <div> Β· Γ9
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/partials/cart/index.jsx:93β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/partials/header/Tools/MonoChrome.jsx:8β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/partials/header/index.jsx:104β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/partials/header/index.jsx:120β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/partials/header/index.jsx:141β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/partials/settings/index.jsx:66β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/partials/sidebar/Logo.jsx:53β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/ui/Alert.jsx:30β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> src/Apps/App.Admin/src/components/ui/Alert.jsx:38β This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> β the right fix for its keyboard operability β does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC1 Β· Text alternativesΒ· <img> without a text alternative Β· Γ5
<img> without a text alternative src/Apps/App.Admin/src/pages/forms/file-input/DropZone.jsx:45β An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt β alt="" if it's purely decorative.
<img> without a text alternative src/Apps/App.Admin/src/pages/product/productDetails.jsx:627β An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt β alt="" if it's purely decorative.
<img> without a text alternative src/Apps/App.Admin/src/pages/product/productDetails.jsx:667β An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt β alt="" if it's purely decorative.
<img> without a text alternative src/Apps/App.Admin/src/pages/product/productDetails.jsx:673β An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt β alt="" if it's purely decorative.
<img> without a text alternative src/Apps/App.Admin/src/pages/product/productDetails.jsx:679β An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt β alt="" if it's purely decorative.
AC4 Β· Keyboard semanticsΒ· Click handler on a non-interactive <span> Β· Γ5
Click handler on a non-interactive <span> src/Apps/App.Admin/src/components/partials/settings/index.jsx:30β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> src/Apps/App.Admin/src/components/ui/InputGroup.jsx:143β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> src/Apps/App.Admin/src/components/ui/Textinput.jsx:97β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> src/Apps/App.Admin/src/pages/app/chat/Blank.jsx:23β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> src/Apps/App.Admin/src/pages/app/chat/Chat.jsx:59β A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC2 Β· Forms & labelsΒ· <input> without a programmatic label Β· Γ4
<input> without a programmatic label src/Apps/App.Admin/src/components/partials/ecommerce/rangeSlider.jsx:19β 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 src/Apps/App.Admin/src/components/partials/ecommerce/rangeSlider.jsx:25β 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 src/Apps/App.Admin/src/components/partials/ecommerce/rangeSlider.jsx:51β 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 src/Apps/App.Admin/src/components/partials/ecommerce/rangeSlider.jsx:60β This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 Β· Keyboard semanticsΒ· Clickable role="button" that no keyboard user can reach Β· Γ3
Clickable role="button" that no keyboard user can reach src/Apps/App.Store/src/components/accordion/FaqAccordionSection.jsx:22β This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach src/Apps/App.Store/src/components/accordion/FaqAccordionSection.jsx:48β This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach src/Apps/App.Store/src/components/mobile-menu/MobileMenuSection.jsx:20β This <i> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Banned license: MySql.EntityFrameworkCore REDACTED:32β `MySql.EntityFrameworkCore` 8.0.5 resolves to SPDX id GPL-2.0-only, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison β which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. β This arm reads the resolved package list and knows nothing about dependency SCOPE β it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. β DEPTH: this repository's MSBuild projects declare 65 direct `PackageReference`(s), and 185 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.
Banned license: MySql.Data REDACTED:48β `MySql.Data` 9.0.0 resolves to SPDX id GPL-2.0-only, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison β which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. β This arm reads the resolved package list and knows nothing about dependency SCOPE β it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. β DEPTH: this repository's MSBuild projects declare 65 direct `PackageReference`(s), and 185 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.
Banned license: Volo.Abp.AspNetCore β `Volo.Abp.AspNetCore` 8.0.0 resolves to SPDX id LGPL-3.0-only, and this run's banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an `OR` is a choice and is charged only when every branch is banned, an `AND` binds every operand, and a `WITH` exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison β which is how variants like `-only` and `-or-later` are caught while `LGPL-2.0-only` is not read as `GPL-2.0`, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. β This arm reads the resolved package list and knows nothing about dependency SCOPE β it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. β DEPTH: this repository's MSBuild projects declare 65 direct `PackageReference`(s), and 185 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. β The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do β that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
AC4 Β· Keyboard semanticsΒ· Click handler on a non-interactive <li> Β· Γ2
Click handler on a non-interactive <li> src/Apps/App.Admin/src/pages/app/todo/BottomFilter.jsx:5β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <li> src/Apps/App.Admin/src/pages/dashboard/banking.jsx:88β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Namespace dependency cycle src/Services/Inventory/Core/Inventory.Domain/Repositories/IInboxMessageRepository.cs:3β The namespaces Inventory.Domain.Abstractions β Inventory.Domain.Entities β Inventory.Domain.Repositories depend on each other. The lightest dependency in the cycle is Inventory.Domain.Repositories β Inventory.Domain.Entities (Inventory.Domain.Repositories.IInboxMessageRepository β Inventory.Domain.Entities.InboxMessageEntity, 3 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.
Namespace dependency cycle src/Services/Order/Core/Order.Domain/Repositories/IInboxMessageRepository.cs:3β The namespaces Order.Domain.Abstractions β Order.Domain.Entities β Order.Domain.Repositories depend on each other. The lightest dependency in the cycle is Order.Domain.Repositories β Order.Domain.Entities (Order.Domain.Repositories.IInboxMessageRepository β Order.Domain.Entities.InboxMessageEntity, 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.
AC4 Β· Keyboard semanticsΒ· Hover-only interaction on <div> Β· Γ1
Hover-only interaction on <div> src/Apps/App.Admin/src/components/partials/sidebar/index.jsx:38β This <div> binds mouse-enter and mouse-leave and nothing else β no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
AC4 Β· Keyboard semanticsΒ· Click handler on a non-interactive <video> Β· Γ1
Click handler on a non-interactive <video> src/Apps/App.Admin/src/components/ui/VideoPlayer.jsx:12β A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
WriteOnlyPrivateField src/Services/Discount/Core/Discount.Infrastructure/Repositories/UnitOfWork.cs:18β private IMongoDatabase _database β 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.
NoWarnInCsproj src/Directory.Build.props:19β CS1591 β this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or β if some occurrences really are legitimate β narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
Orphaned knowledge src/Services/Catalog/Core/Catalog.Infrastructure/Data/ProductSeedData.cs:1β No living knowledge remains for this large file β its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
No automated tests β No automated tests β no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
TLS certificate validation disabled src/Services/Inventory/Core/Inventory.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:29β `ServerCertificateCustomValidationCallback` is assigned `DangerousAcceptAnyServerCertificateValidator`, so every TLS peer certificate is accepted β including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic β the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one β compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else β and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship.
FunctionTooLong: index.InventoryPage src/Apps/App.Admin/src/pages/inventory/index.jsx:53β FunctionTooLong β InventoryPage runs 1463 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1363 over it, 14.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body β the runs of statements that work on the same values and would earn the same name β into its own named unit, and have this one call them in order.
FunctionTooLong: index.CouponPage src/Apps/App.Admin/src/pages/coupon/index.jsx:36β FunctionTooLong β CouponPage runs 887 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 787 over it, 8.87× 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: FarzaaContext.FarzaaContextProvider src/Apps/App.Store/src/context/FarzaaContext.jsx:14β FunctionTooLong β FarzaaContextProvider runs 806 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 706 over it, 8.06× 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: index.Orders src/Apps/App.Admin/src/pages/orders/index.jsx:88β FunctionTooLong β Orders runs 663 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 563 over it, 6.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body β the runs of statements that work on the same values and would earn the same name β into its own named unit, and have this one call them in order.
FunctionTooLong: index.CategoryPage src/Apps/App.Admin/src/pages/category/index.jsx:36β FunctionTooLong β CategoryPage runs 645 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 545 over it, 6.45× 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: edit-product.EditProduct src/Apps/App.Admin/src/pages/product/edit-product.jsx:17β FunctionTooLong β EditProduct runs 620 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 520 over it, 6.20× 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: index.Ecommerce src/Apps/App.Admin/src/pages/product/index.jsx:43β FunctionTooLong β Ecommerce runs 585 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 485 over it, 5.85× 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: create-product.CreateProduct src/Apps/App.Admin/src/pages/product/create-product.jsx:17β FunctionTooLong β CreateProduct runs 572 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 472 over it, 5.72× 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: productDetails.ProductDetails src/Apps/App.Admin/src/pages/product/productDetails.jsx:35β FunctionTooLong β ProductDetails runs 572 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 472 over it, 5.72× 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: modal.ModalPage src/Apps/App.Admin/src/pages/components/modal.jsx:7β FunctionTooLong β ModalPage runs 560 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 460 over it, 5.60× 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: index.BrandPage src/Apps/App.Admin/src/pages/brand/index.jsx:35β FunctionTooLong β BrandPage runs 537 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 437 over it, 5.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body β the runs of statements that work on the same values and would earn the same name β into its own named unit, and have this one call them in order.
FunctionTooLong: details.OrderDetails src/Apps/App.Admin/src/pages/orders/details.jsx:63β FunctionTooLong β OrderDetails runs 512 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 412 over it, 5.12× 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: dropdown.dropdown src/Apps/App.Admin/src/pages/components/dropdown.jsx:7β FunctionTooLong β dropdown runs 502 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 402 over it, 5.02× 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: typography.typography src/Apps/App.Admin/src/pages/components/typography.jsx:24β FunctionTooLong β typography runs 453 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 353 over it, 4.53× 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: add-product.AddProduct src/Apps/App.Admin/src/pages/product/add-product.jsx:9β FunctionTooLong β AddProduct runs 453 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 353 over it, 4.53× 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: card.card src/Apps/App.Admin/src/pages/components/card.jsx:115β FunctionTooLong β card runs 434 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 334 over it, 4.34× 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: CheckoutSection.CheckoutSection src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:15β FunctionTooLong β CheckoutSection runs 417 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 317 over it, 4.17× 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: edit.EditOrder src/Apps/App.Admin/src/pages/orders/edit.jsx:18β FunctionTooLong β EditOrder runs 408 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 308 over it, 4.08× 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: orders.Orders src/Apps/App.Admin/src/pages/product/orders.jsx:160β FunctionTooLong β Orders runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× 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: create.CreateOrder src/Apps/App.Admin/src/pages/orders/create.jsx:17β FunctionTooLong β CreateOrder runs 379 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 279 over it, 3.79× 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: edit-coupon.EditCoupon src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:16β FunctionTooLong β EditCoupon runs 365 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 265 over it, 3.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body β the runs of statements that work on the same values and would earn the same name β into its own named unit, and have this one call them in order.
FunctionTooLong: alert.alert src/Apps/App.Admin/src/pages/components/alert.jsx:6β FunctionTooLong β alert runs 364 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 264 over it, 3.64× 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: create-coupon.CreateCoupon src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:15β FunctionTooLong β CreateCoupon runs 341 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 241 over it, 3.41× 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: index.NotificationPage src/Apps/App.Admin/src/pages/notification/index.jsx:53β FunctionTooLong β NotificationPage runs 339 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 239 over it, 3.39× 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: orderDetails.OrderDetails src/Apps/App.Admin/src/pages/product/orderDetails.jsx:77β FunctionTooLong β OrderDetails runs 330 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 230 over it, 3.30× 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.
Dead code: PaginatedResult src/Shared/BuildingBlocks/Pagination/PaginatedResult.cs:3β NamedType PaginatedResult β Roslyn's SymbolFinder walked every project the solution loads, including BuildingBlocks, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MustHave src/Shared/BuildingBlocks/Validators/CustomValidators.cs:14β Method MustHave β Roslyn's SymbolFinder walked every project the solution loads, including BuildingBlocks, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CorsCfg src/Shared/Common/Configurations/CorsCfg.cs:3β NamedType CorsCfg β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: FileContentType src/Shared/Common/Constants/AppConstants.cs:47β NamedType FileContentType β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: UseSha256 src/Shared/Common/Extensions/HashExtension.cs:14β Method UseSha256 β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: UseSha256 src/Shared/Common/Extensions/HashExtension.cs:27β Method UseSha256 β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: UseSha512 src/Shared/Common/Extensions/HashExtension.cs:40β Method UseSha512 β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToFileSize src/Shared/Common/Extensions/NumericExtension.cs:13β Method ToFileSize β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToShortNumber src/Shared/Common/Extensions/NumericExtension.cs:26β Method ToShortNumber β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToEnum src/Shared/Common/Extensions/NumericExtension.cs:51β Method ToEnum β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: WhereIf src/Shared/Common/Extensions/QueryableExtension.cs:13β Method WhereIf β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TakeIf src/Shared/Common/Extensions/QueryableExtension.cs:25β Method TakeIf β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: PageBy src/Shared/Common/Extensions/QueryableExtension.cs:37β Method PageBy β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TruncateString src/Shared/Common/Extensions/StringExtension.cs:13β Method TruncateString β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToEnum src/Shared/Common/Extensions/StringExtension.cs:31β Method ToEnum β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: To src/Shared/Common/Extensions/StringExtension.cs:39β Method To β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EnumHelper src/Shared/Common/Helpers/EnumHelper.cs:3β NamedType EnumHelper β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: NumericHelper src/Shared/Common/Helpers/NumericHelper.cs:3β NamedType NumericHelper β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: HasRoles src/Shared/Common/Models/Context/UserContext.cs:29β Method HasRoles β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Job src/Shared/Common/ValueObjects/Actor.cs:15β Method Job β Roslyn's SymbolFinder walked every project the solution loads, including Common, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ApplicationMarker src/Services/Catalog/Core/Catalog.Application/ApplicationMarker.cs:3β NamedType ApplicationMarker β Roslyn's SymbolFinder walked every project the solution loads, including Catalog.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: EntityDto src/Services/Catalog/Core/Catalog.Application/Dtos/Abstractions/EntityDto.cs:3β NamedType EntityDto β Roslyn's SymbolFinder walked every project the solution loads, including Catalog.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetShareLinkAsync src/Services/Catalog/Core/Catalog.Application/Services/IMinIOCloudService.cs:13β Method GetShareLinkAsync β Roslyn's SymbolFinder walked every project the solution loads, including Catalog.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CanRetry src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:100β Method CanRetry β Roslyn's SymbolFinder walked every project the solution loads, including Catalog.Domain, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ApplicationMarker src/Services/Inventory/Core/Inventory.Application/ApplicationMarker.cs:3β NamedType ApplicationMarker β Roslyn's SymbolFinder walked every project the solution loads, including Inventory.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository β a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
+ 37 more in this group β see findings.md.
D31 Β· IaC & Container SecurityΒ· Medium IaC Β· Γ56
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 31 more in this group β see findings.md.
X2 Β· Cancellation propagationΒ· Async method without CancellationToken Β· Γ39
Async method without CancellationToken: HandleCreateBrandAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateBrand.cs:31β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleCreateCategoryAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateCategory.cs:31β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleCreateProductAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs:41β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleDeleteBrandAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/DeleteBrand.cs:28β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleDeleteCategoryAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/DeleteCategory.cs:28β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleDeleteProductAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/DeleteProduct.cs:32β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetAllBrandsAsync REDACTED:28β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetAllCategoriesAsync REDACTED:29β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetAllProductsAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/GetAllProducts.cs:31β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetProductByIdAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/GetProductById.cs:32β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetProductsAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/GetProducts.cs:32β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetPublishProductByIdAsync REDACTED:31β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetPublishProductsAsync REDACTED:31β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleGetTreeCategoriesAsync REDACTED:29β No CancellationToken parameter β this work can't be stopped early once started.
Async method without CancellationToken: HandleInitializeDataAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/InitializeData.cs:29β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandlePublishProductAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/PublishProduct.cs:32β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleUnpublishProductAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/UnpublishProduct.cs:33β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleUpdateBrandAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/UpdateBrand.cs:31β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleUpdateCategoryAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/UpdateCategory.cs:31β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleUpdateProductAsync src/Services/Catalog/Api/Catalog.Api/Endpoints/UpdateProduct.cs:41β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: GetProductById src/Services/Catalog/Api/Catalog.Grpc/Services/CatalogGrpcService.cs:16β No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken.
Async method without CancellationToken: GetProducts src/Services/Catalog/Api/Catalog.Grpc/Services/CatalogGrpcService.cs:32β No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken.
Async method without CancellationToken: GetCountProduct src/Services/Catalog/Api/Catalog.Grpc/Services/CatalogGrpcService.cs:54β No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken.
Async method without CancellationToken: GetAllAvailableProducts src/Services/Catalog/Api/Catalog.Grpc/Services/CatalogGrpcService.cs:65β No CancellationToken parameter, and the token `context.CancellationToken` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `context.CancellationToken` on, or take a CancellationToken.
Async method without CancellationToken: HandleCreateInventoryItemAsync src/Services/Inventory/Api/Inventory.Api/Endpoints/CreateInventoryItem.cs:32β No CancellationToken parameter, and the token `httpContext.HttpContext.RequestAborted` carries reaches none of the calls here that take one β this work can't be stopped early once started. Pass `httpContext.HttpContext.RequestAborted` on, or take a CancellationToken.
+ 14 more in this group β see findings.md.
DM12 Β· Ambient inputs in the domainΒ· Domain type reads the wall clock Β· Γ38
Domain type reads the wall clock: BasketCheckoutDomainEventHandler src/Services/Basket/Core/Basket.Application/Features/Basket/EventHandlers/Domain/BasketCheckoutDomainEventHandler.cs:70β `BasketCheckoutDomainEventHandler` reads `DateTimeOffset.UtcNow` inside `PushToOutboxAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: BrandEntity src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs:33β `BrandEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: BrandEntity src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs:34β `BrandEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: BrandEntity src/Services/Catalog/Core/Catalog.Domain/Entities/BrandEntity.cs:49β `BrandEntity` reads `DateTimeOffset.UtcNow` inside `Update`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CategoryEntity src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:41β `CategoryEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CategoryEntity src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:42β `CategoryEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CategoryEntity src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:61β `CategoryEntity` reads `DateTimeOffset.UtcNow` inside `Update`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:83β `CouponEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:85β `CouponEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:110β `CouponEntity` reads `DateTimeOffset.UtcNow` inside `Update`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:120β `CouponEntity` reads `DateTimeOffset.UtcNow` inside `Approve`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:130β `CouponEntity` reads `DateTimeOffset.UtcNow` inside `Reject`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:178β `CouponEntity` reads `DateTimeOffset.UtcNow` inside `UpdateValidityPeriod`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:185β `CouponEntity` reads `DateTime.UtcNow` inside `IsValid`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:186β `CouponEntity` reads `DateTime.UtcNow` inside `IsValid`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:197β `CouponEntity` reads `DateTime.UtcNow` inside `IsExpired`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:51β `DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:52β `DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:69β `DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `UpdateCount`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:78β `DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `UpdateDisplay`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DeletedUnPublishedProductDomainEventHandler src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/DeletedUnPublishedProductDomainEventHandler.cs:44β `DeletedUnPublishedProductDomainEventHandler` reads `DateTimeOffset.UtcNow` inside `PushToOutboxAsync`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:73β `DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:74β `DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `Create`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:82β `DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `UpdateStatus`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:83β `DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `UpdateStatus`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
+ 13 more in this group β see findings.md.
D30 Β· Dependency VulnerabilitiesΒ· Medium CVE Β· Γ20
AC6 Β· Visual & motion safetyΒ· Animation without a prefers-reduced-motion guard Β· Γ16
Animation without a prefers-reduced-motion guard src/Apps/App.Admin/src/components/Loader-circle.jsx:7β <div> moves β its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant β and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/Apps/App.Admin/src/components/Loading.jsx:16β <svg> moves β its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant β and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/Apps/App.Admin/src/components/ui/Button.jsx:55β <svg> moves β its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant β and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/Apps/App.Admin/src/components/ui/Button.jsx:116β <svg> moves β its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant β and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/Apps/App.Admin/src/components/ui/Button.jsx:177β <svg> moves β its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant β and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:80β `.icon-line.line-tip` moves (`animation: icon-line-tip 0.75s`) 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 src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:88β `.icon-line.line-long` moves (`animation: icon-line-long 0.75s`) 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 src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:175β `.success-title` moves (`animation: fadeInUp 0.6s ease 0.3s backwards`) 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 src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:183β `.success-message` moves (`animation: fadeInUp 0.6s ease 0.4s backwards`) 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 src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:191β `.order-number` moves (`animation: fadeInUp 0.6s ease 0.5s backwards`) 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 src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:211β `.success-note` moves (`animation: fadeInUp 0.6s ease 0.6s backwards`) 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 src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:226β `.success-btn` moves (`animation: fadeInUp 0.6s ease 0.7s backwards`) 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 src/Apps/App.Store/src/components/modal/OrderSuccessModal.css:285β `.confetti` moves (`animation: confetti-fall 3s ease-out forwards`) 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 src/Apps/App.Store/public/assets/scss/sections/_banner.scss:194β `.fz-3-banner-section .fz-3-banner-product-cards .fz-3-single-product` moves (`animation: upDown 2s linear infinite alternate`) 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 src/Apps/App.Store/public/assets/scss/sections/_banner.scss:540β `.fz-2-banner-section .fz-banner-vid .fz-banner-rounded-sticker .fz-rotateText` moves (`animation: rotateText 6s linear infinite`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/Apps/App.Store/public/assets/scss/sections/_banner.scss:793β `.fz-1-banner-section .fz-1-banner-img-container .sticker-container .sticker` moves (`animation: rotateText 6s linear infinite`) and nothing reads prefers-reduced-motion for it β no @media (prefers-reduced-motion) rule for this element, no reset this project loads β so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
FileTooLong: inventory/index.jsx src/Apps/App.Admin/src/pages/inventory/index.jsxβ FileTooLong β 1506 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: InventoryPage (53-1808). The bar is 500 significant lines; this is 1006 over it, 3.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: coupon/index.jsx src/Apps/App.Admin/src/pages/coupon/index.jsxβ FileTooLong β 918 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: CouponPage (36-1082). The bar is 500 significant lines; this is 418 over it, 1.84× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: context/FarzaaContext.jsx src/Apps/App.Store/src/context/FarzaaContext.jsxβ FileTooLong β 818 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: FarzaaContextProvider (14-1244). The bar is 500 significant lines; this is 318 over it, 1.64× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: orders/index.jsx src/Apps/App.Admin/src/pages/orders/index.jsxβ FileTooLong β 732 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: Orders (88-908). The bar is 500 significant lines; this is 232 over it, 1.46× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: category/index.jsx src/Apps/App.Admin/src/pages/category/index.jsxβ FileTooLong β 676 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: CategoryPage (36-807). The bar is 500 significant lines; this is 176 over it, 1.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: product/edit-product.jsx src/Apps/App.Admin/src/pages/product/edit-product.jsxβ FileTooLong β 636 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: EditProduct (17-747). The bar is 500 significant lines; this is 136 over it, 1.27× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: product/index.jsx src/Apps/App.Admin/src/pages/product/index.jsxβ FileTooLong β 620 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Ecommerce (43-737). The bar is 500 significant lines; this is 120 over it, 1.24× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: product/productDetails.jsx src/Apps/App.Admin/src/pages/product/productDetails.jsxβ FileTooLong β 604 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ProductDetails (35-710). The bar is 500 significant lines; this is 104 over it, 1.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: product/create-product.jsx src/Apps/App.Admin/src/pages/product/create-product.jsxβ FileTooLong β 588 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: CreateProduct (17-680). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: brand/index.jsx src/Apps/App.Admin/src/pages/brand/index.jsxβ FileTooLong β 567 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: BrandPage (35-677). The bar is 500 significant lines; this is 67 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: components/modal.jsx src/Apps/App.Admin/src/pages/components/modal.jsxβ FileTooLong β 566 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: ModalPage (7-604). The bar is 500 significant lines; this is 66 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: orders/details.jsx src/Apps/App.Admin/src/pages/orders/details.jsxβ FileTooLong β 560 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: OrderDetails (63-661). The bar is 500 significant lines; this is 60 over it, 1.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: components/dropdown.jsx src/Apps/App.Admin/src/pages/components/dropdown.jsxβ FileTooLong β 508 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: dropdown (7-543). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: components/card.jsx src/Apps/App.Admin/src/pages/components/card.jsxβ FileTooLong β 506 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: card (115-555). The bar is 500 significant lines; this is 6 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
FileTooLong: product/orders.jsx src/Apps/App.Admin/src/pages/product/orders.jsxβ FileTooLong β 505 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: Orders (160-604). The bar is 500 significant lines; this is 5 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body β the parts that share the same inputs and are named together β into its own unit in a sibling file, and have the original call them.
AC3 Β· Page structureΒ· Heading level jumps from h4 to h6 Β· Γ10
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/banner/BannerSection10.jsx:105β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/blog/BlogDetailSection.jsx:82β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/feature/FeatureSection.jsx:14β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/feature/FeatureSection.jsx:24β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/feature/FeatureSection.jsx:34β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/feature/FeatureSection.jsx:44β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/featured/FeaturedSection.jsx:14β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/featured/FeaturedSection.jsx:24β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/featured/FeaturedSection.jsx:34β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h4 to h6 src/Apps/App.Store/src/components/featured/FeaturedSection.jsx:44β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
AC3 Β· Page structureΒ· Heading level jumps from h2 to h4 Β· Γ8
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/banner/SubBannerSection3.jsx:17β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/banner/SubBannerSection3.jsx:35β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/blog/BagBlogSection.jsx:24β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/blog/BagBlogSection2.jsx:55β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/blog/BlogSection6.jsx:72β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/blog/BlogSection7.jsx:55β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/blog/BlogSection8.jsx:34β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h4 src/Apps/App.Store/src/components/blog/KidsBlogSection.jsx:63β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
DM11 Β· Constructible invalid stateΒ· Constructible in an invalid state Β· Γ8
Constructible in an invalid state: InventoryItemEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs:14β `InventoryItemEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Quantity`, `Reserved`, so `new InventoryItemEntity { Quantity = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Constructible in an invalid state: InventoryReservationEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs:12β `InventoryReservationEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Quantity`, so `new InventoryReservationEntity { Quantity = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Constructible in an invalid state: LocationEntity src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs:9β `LocationEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Location`, so `new LocationEntity { Location = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Constructible in an invalid state: OrderItemEntity src/Services/Order/Core/Order.Domain/Entities/OrderItemEntity.cs:10β `OrderItemEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Quantity`, so `new OrderItemEntity { Quantity = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Constructible in an invalid state: CouponEntity src/Services/Discount/Core/Discount.Domain/Entities/CouponEntity.cs:10β `CouponEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Code`, `Name`, `Description`, `Value`, β¦, so `new CouponEntity { Code = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Constructible in an invalid state: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:9β `DashboardTotalEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Bg`, `Text`, `Icon`, `Title`, β¦, so `new DashboardTotalEntity { Bg = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Constructible in an invalid state: OrderGrowthLineChartEntity src/Services/Report/Core/Report.Domain/Entities/OrderGrowthLineChartEntity.cs:9β `OrderGrowthLineChartEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Day`, `Value`, so `new OrderGrowthLineChartEntity { Day = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Constructible in an invalid state: TopProductPieChartEntity src/Services/Report/Core/Report.Domain/Entities/TopProductPieChartEntity.cs:9β `TopProductPieChartEntity` validates on one way in (`Create`) but also has a public parameterless constructor (the implicit one β no constructor is declared) and public setters for `Name`, `Value`, so `new TopProductPieChartEntity { Name = β¦ }` builds an instance that check never saw. What was searched, so you can tell an absence from a miss: each public `set`/`init` of a `string` or number property was scanned for the same guard tokens as a constructor; an auto-property has no body and refuses nothing. If those setters validate through something this search does not name, this row is wrong. If they do not, make the setters private (or `init` behind a guarded constructor) and the parameterless constructor private or protected for the ORM, so the validating way in is the only one.
Deprecated: AutoMapper.Extensions.Microsoft.DependencyInjection REDACTED:20β AutoMapper.Extensions.Microsoft.DependencyInjection 12.0.1 β Legacy β the publisher's replacement is `AutoMapper` >= 13.0.0; migrate the reference to it.
Deprecated: Polly.Extensions.Http REDACTED:102β Polly.Extensions.Http 3.0.0 β Legacy β the publisher's replacement is `Microsoft.Extensions.Http.Resilience`; migrate the reference to it.
Deprecated: Elasticsearch.Net REDACTED:56β Elasticsearch.Net 7.17.5 β Legacy β the publisher's replacement is `Elastic.Clients.Elasticsearch`; migrate the reference to it.
Deprecated: NEST REDACTED:57β NEST 7.17.5 β Legacy β the publisher's replacement is `Elastic.Clients.Elasticsearch`; migrate the reference to it.
Deprecated: recharts src/Apps/App.Admin/package.json:67β recharts 2.15.4, declared in src/Apps/App.Admin/package.json, is marked deprecated by its publisher: "1.x and 2.x branches are no longer active. Bump to Recharts v3 to receive latest features and bugfixes. See https://github.com/recharts/recharts/wiki/3.0-migration-guide". Replace it with the package or version that message names, or record why this one must stay.
Low contrast Tailwind colour pair (3.8:1) src/Apps/App.Admin/src/components/partials/footer/MobileFooter.jsx:18β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) src/Apps/App.Admin/src/components/partials/footer/MobileFooter.jsx:63β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) src/Apps/App.Admin/src/components/partials/header/Tools/Message.jsx:12β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) src/Apps/App.Admin/src/components/partials/header/Tools/Notification.jsx:134β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) src/Apps/App.Admin/src/components/partials/header/Tools/cart.jsx:21β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (3.8:1) src/Apps/App.Admin/src/pages/components/progress-bar/step.jsx:36β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Sync-over-async blocking β 5 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) β these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16β `.GetAwaiter().GetResult()` blocks this thread until the async work completes β it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:80β `.GetAwaiter().GetResult()` blocks this thread until the async work completes β it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16β `.GetAwaiter().GetResult()` blocks this thread until the async work completes β it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:78β `.Wait()` blocks this thread until the async work completes β it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Services/Search/Core/Search.Infrastructure/DependencyInjection.cs:66β `.GetAwaiter().GetResult()` blocks this thread until the async work completes β it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
AC3 Β· Page structureΒ· Heading level jumps from h2 to h6 Β· Γ5
Heading level jumps from h2 to h6 src/Apps/App.Store/src/components/banner/SubBannerSection.jsx:34β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h6 src/Apps/App.Store/src/components/banner/SubBannerSection.jsx:53β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h6 src/Apps/App.Store/src/components/banner/SubBannerSection2.jsx:13β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h6 src/Apps/App.Store/src/components/banner/SubBannerSection2.jsx:32β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h6 src/Apps/App.Store/src/components/category/CategorySection5.jsx:15β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Low contrast Tailwind colour pair (4.3:1) src/Apps/App.Admin/src/pages/auth/forgot-password.jsx:53β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.3:1) src/Apps/App.Admin/src/pages/auth/forgot-password2.jsx:33β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.3:1) src/Apps/App.Admin/src/pages/auth/forgot-password3.jsx:43β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.3:1) src/Apps/App.Admin/src/pages/auth/lock-screen2.jsx:44β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast Tailwind colour pair (4.3:1) src/Apps/App.Admin/src/pages/notification/index.jsx:216β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Duplicated block (19 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:84β src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:84-102 | src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:130-148 β 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 `src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:84` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows β the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run β a one-line delegation has no helper inside it to lift β so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:9β src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:9-27 | src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs:9-27 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs` and `src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:88β src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:88-106 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:86-104 β before extracting anything, compare `src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.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 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:88` 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 (19 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:88β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:88-106 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:86-104 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs` and `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.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 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:88` 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 (19 lines × 2) src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:76β src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:76-94 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/Processors/OutboxProcessor.cs:87-105 β before extracting anything, compare `src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs` and `src/Services/Catalog/Worker/Catalog.Woker.Outbox/Processors/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 103 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 `src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:76` it runs out through the closing brace of the declaration holding it β the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:141β src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:141-153 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:174-186 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/Services/Order/Core/Order.Application/Dtos/ValueObjects/AddressDto.cs:5β src/Services/Order/Core/Order.Application/Dtos/ValueObjects/AddressDto.cs:5-17 | src/Services/Order/Core/Order.Domain/ValueObjects/Address.cs:5-17 β 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 (13 lines × 2) src/Services/Order/Core/Order.Application/Models/Filters/GetAllOrdersFilter.cs:11β src/Services/Order/Core/Order.Application/Models/Filters/GetAllOrdersFilter.cs:11-23 | src/Services/Order/Core/Order.Application/Models/Filters/GetOrdersFilter.cs:11-23 β before extracting anything, compare `src/Services/Order/Core/Order.Application/Models/Filters/GetAllOrdersFilter.cs` and `src/Services/Order/Core/Order.Application/Models/Filters/GetOrdersFilter.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. 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 (13 lines × 2) src/JobOrchestrator/App.Job/Jobs/Inventory/ExpireInventoryReservationsJob.cs:34β src/JobOrchestrator/App.Job/Jobs/Inventory/ExpireInventoryReservationsJob.cs:34-49 | src/JobOrchestrator/App.Job/Jobs/Report/SyncDashboardReportJob.cs:52-64 β 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 `src/JobOrchestrator/App.Job/Jobs/Inventory/ExpireInventoryReservationsJob.cs:34` 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 (13 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.cs:18β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.cs:18-30 | src/Services/Order/Core/Order.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.cs:18-30 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.cs` and `src/Services/Order/Core/Order.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Sync-over-async (deadlock risk) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16β Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay β a public sync API you cannot break, or a process entry point that must not return until the work finishes β the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:80β Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay β a public sync API you cannot break, or a process entry point that must not return until the work finishes β the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:16β Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay β a public sync API you cannot break, or a process entry point that must not return until the work finishes β the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:78β Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay β a public sync API you cannot break, or a process entry point that must not return until the work finishes β the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Services/Search/Core/Search.Infrastructure/DependencyInjection.cs:66β Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay β a public sync API you cannot break, or a process entry point that must not return until the work finishes β the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
AC6 Β· Visual & motion safetyΒ· Focus outline removed in CSS without a Β· Γ4
Focus outline removed in CSS without a :focus replacement src/Apps/App.Store/public/assets/scss/sections/_featured-products.scss:2069β `.fz-11-feature .fz-11-feature-tab1 li button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/Apps/App.Store/public/assets/scss/sections/_featured-products.scss:2091β `.fz-11-feature .fz-11-feature-tab button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/Apps/App.Store/public/assets/scss/main/_global.scss:189β `input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/Apps/App.Store/public/assets/scss/main/_utils.scss:44β `.wrapper .rv-container input[type="range"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
ClassTooLong: dropdown src/Apps/App.Admin/src/pages/components/dropdown.jsx:1β ClassTooLong β 502 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 102 over it, 1.26× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: typography src/Apps/App.Admin/src/pages/components/typography.jsx:1β ClassTooLong β 453 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 53 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: card src/Apps/App.Admin/src/pages/components/card.jsx:1β ClassTooLong β 434 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 34 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CheckoutSection src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:1β ClassTooLong β 417 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 17 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 Β· Code DuplicationΒ· Members sharing a duplicated core (5 members, 50+ identical tokens) Β· Γ4
Members sharing a duplicated core (5 members, 50+ identical tokens) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:22β src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:22-83 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:22-85 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:25-91 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductByIdQuery.cs:21-57 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductsQuery.cs:25-84 β 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:74β src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:74-93 | src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:74-93 | src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:74-93 | src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.cs:66-85 | src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs:66-85 β 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryHistoryConfiguration.cs:16β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryHistoryConfiguration.cs:16-44 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:16-69 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryReservationConfiguration.cs:16-80 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OrderEntityConfiguration.cs:16-147 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OrderItemEntityConfiguration.cs:16-69 β 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:20β src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:20-38 | src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 | src/Services/Inventory/Core/Inventory.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 | src/Services/Order/Core/Order.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 | src/Services/Report/Core/Report.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 β 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.
D4 Β· Code DuplicationΒ· Members sharing a duplicated core (4 members, 50+ identical tokens) Β· Γ4
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:16β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:16-43 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:16-61 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:16-61 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:16-61 β 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) src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:34β src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:34-39 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:34-39 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:35-40 | src/Services/Order/Worker/Order.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:34-39 β 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) src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:76β src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:76-95 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:76-95 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:77-96 | src/Services/Order/Worker/Order.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:76-95 β 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) src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCancelledIntegrationEventHandler.cs:26β src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCancelledIntegrationEventHandler.cs:26-79 | src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderDeliveredIntegrationEventHandler.cs:26-85 | src/Services/Order/Worker/Order.Worker.Consumer/EventHandlers/Integrations/BasketCheckoutIntegrationEventHandler.cs:27-102 | src/Services/Order/Worker/Order.Worker.Consumer/EventHandlers/Integrations/ReservationExpiredIntegrationEventHandler.cs:27-84 β 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 (30 lines × 2) src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs:55β src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs:55-84 | src/Services/Catalog/Api/Catalog.Api/Endpoints/UpdateProduct.cs:56-85 β 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 (30 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:74β src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:74-103 | src/Services/Order/Core/Order.Infrastructure/Services/CatalogGrpcService.cs:74-103 β before extracting anything, compare `src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs` and `src/Services/Order/Core/Order.Infrastructure/Services/CatalogGrpcService.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:22β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:22-51 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:22-51 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.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 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:22β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:22-51 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:22-51 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/PostgreSqlDatabaseProvider.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/Services/Search/Core/Search.Application/Dtos/Products/ProductDto.cs:14β src/Services/Search/Core/Search.Application/Dtos/Products/ProductDto.cs:14-30 | src/Services/Search/Core/Search.Application/Dtos/Products/UpsertProductDto.cs:15-31 β 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 (17 lines × 2) src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/InventoryItemDeletedDomainEventHandler.cs:36β src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/InventoryItemDeletedDomainEventHandler.cs:36-52 | src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/StockChangedDomainEventHandler.cs:36-52 β the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach β a file they already depend on, or a new one alongside them β and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs:36β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs:36-52 | src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs:36-52 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs` and `src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Models/OutboxMessage.cs:3β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Models/OutboxMessage.cs:3-19 | src/Services/Order/Worker/Order.Woker.Outbox/Models/OutboxMessage.cs:3-19 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Models/OutboxMessage.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Models/OutboxMessage.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Models/OutboxMessage.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 (9 lines × 5) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:27β src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:27-35 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:29-37 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:27-35 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:35-43 | src/Services/Catalog/Core/Catalog.Domain/Entities/ProductEntity.cs:38-46 β before extracting anything, compare `src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs` and `src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:27β src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:27-35 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:29-37 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:27-35 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/ProductInfoDto.cs:34-42 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:35-43 β before extracting anything, compare `src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs` and `src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) src/Services/Catalog/Api/Catalog.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:32β src/Services/Catalog/Api/Catalog.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:32-40 | src/Services/Discount/Api/Discount.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:32-40 | src/Services/Inventory/Api/Inventory.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:32-40 | src/Services/Order/Api/Order.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:32-40 | src/Services/Report/Api/Report.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:32-40 β before extracting anything, compare `src/Services/Catalog/Api/Catalog.Grpc/Interceptors/ApiKeyValidationInterceptor.cs` and `src/Services/Discount/Api/Discount.Grpc/Interceptors/ApiKeyValidationInterceptor.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 5) src/Services/Catalog/Worker/Catalog.Worker.Consumer/BackgroundServices/CatalogBackgroudService.cs:9β src/Services/Catalog/Worker/Catalog.Worker.Consumer/BackgroundServices/CatalogBackgroudService.cs:9-17 | src/Services/Inventory/Worker/Inventory.Worker.Consumer/BackgroundServices/InventoryBackgroudService.cs:9-17 | src/Services/Notification/Worker/Notification.Worker.Consumer/BackgroundServices/NotificationBackgroundService.cs:9-17 | src/Services/Order/Worker/Order.Worker.Consumer/BackgroundServices/OrderBackgroudService.cs:9-17 | src/Services/Search/Worker/Search.Worker.Consumer/BackgroundServices/SearchBackgroudService.cs:9-17 β the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. 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.
DM10 Β· One transaction, one aggregateΒ· One operation mutates 2 aggregates Β· Γ4
One operation mutates 2 aggregates: CommitReservationCommandHandler.Handle src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/CommitReservationCommand.cs:34β `CommitReservationCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: ExpireReservationCommandHandler.Handle src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ExpireReservationCommand.cs:31β `ExpireReservationCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: ReleaseReservationCommandHandler.Handle src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ReleaseReservationCommand.cs:39β `ReleaseReservationCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
One operation mutates 2 aggregates: ReserveInventoryCommandHandler.Handle src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ReserveInventoryCommand.cs:53β `ReserveInventoryCommandHandler.Handle` saves `InventoryItemEntity`, `InventoryReservationEntity` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated β into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
X18 Β· Disposal-pattern correctnessΒ· Disposes a dependency it does not own Β· Γ4
Disposes a dependency it does not own src/Services/Inventory/Core/Inventory.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:29β `transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 29). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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 src/Services/Inventory/Core/Inventory.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:35β `transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 35). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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 src/Services/Order/Core/Order.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:26β `transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 26). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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 src/Services/Order/Core/Order.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:31β `transaction` is never created by `DbTransactionAdapter` β every assignment to it takes a constructor parameter β yet this type disposes it here (line 31). Its declared type `IDbContextTransaction` is an interface, so the instance came from whoever chose and created 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.
AC3 Β· Page structureΒ· Heading level jumps from h1 to h6 Β· Γ3
Heading level jumps from h1 to h6 src/Apps/App.Admin/src/pages/product/productDetails.jsx:546β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h1 to h6 src/Apps/App.Store/src/components/banner/BannerSection6.jsx:62β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h1 to h6 src/Apps/App.Store/src/components/banner/BannerSection7.jsx:102β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
AC3 Β· Page structureΒ· Heading level jumps from h1 to h4 Β· Γ3
Heading level jumps from h1 to h4 src/Apps/App.Store/src/components/banner/BannerSection10.jsx:60β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h1 to h4 src/Apps/App.Store/src/components/banner/BannerSection2.jsx:44β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h1 to h4 src/Apps/App.Store/src/components/banner/BannerSection9.jsx:64β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
AC3 Β· Page structureΒ· Heading level jumps from h3 to h5 Β· Γ3
Heading level jumps from h3 to h5 src/Apps/App.Store/src/components/blog/BlogDetailSection.jsx:37β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h3 to h5 src/Apps/App.Store/src/components/blog/RecentBlogSection.jsx:21β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h3 to h5 src/Apps/App.Store/src/components/category/CategorySection6.jsx:37β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Duplicated block (28 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:58β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:58-85 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:58-85 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.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 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 (28 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:22β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:22-49 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:22-49 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.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 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 (28 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:56β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:56-83 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:56-83 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.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 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 (24 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:17β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:17-40 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:17-40 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs` and `src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 (24 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:58β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:58-81 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:58-81 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/PostgreSqlDatabaseProvider.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:79β src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:79-102 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:82-105 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:79` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `CreateProductCommand` in one and `UpdateProductCommand` 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) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:5β src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:5-17 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:5-17 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:5-17 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:9-21 β before extracting anything, compare `src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs` and `src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9β src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9-21 | src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:9-21 | src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:9-21 | src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs:9-21 β before extracting anything, compare `src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs` and `src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.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 `src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) src/Services/Catalog/Core/Catalog.Domain/Abstractions/Entity.cs:3β src/Services/Catalog/Core/Catalog.Domain/Abstractions/Entity.cs:3-15 | src/Services/Inventory/Core/Inventory.Domain/Abstractions/Entity.cs:3-15 | src/Services/Order/Core/Order.Domain/Abstractions/Entity.cs:3-15 | src/Services/Search/Core/Search.Domain/Abstractions/Entity.cs:3-15 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Domain/Abstractions/Entity.cs` and `src/Services/Inventory/Core/Inventory.Domain/Abstractions/Entity.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 `src/Services/Catalog/Core/Catalog.Domain/Abstractions/Entity.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 (10 lines × 2) src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/CreateCouponCommand.cs:46β src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/CreateCouponCommand.cs:46-55 | src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/UpdateCouponCommand.cs:43-52 β 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 (10 lines × 2) src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:33β src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:33-42 | src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:93-102 β 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:103` calls `Limit` and `src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:43` 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 (10 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:157β src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:157-166 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:190-199 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:40β src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:40-45 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductsQuery.cs:36-41 β 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 (6 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:26β src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:26-31 | src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:25-30 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs` and `src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 (6 lines × 2) src/Services/Order/Core/Order.Application/Features/Order/Queries/GetAllMyOrdersQuery.cs:30β src/Services/Order/Core/Order.Application/Features/Order/Queries/GetAllMyOrdersQuery.cs:30-35 | src/Services/Order/Core/Order.Application/Features/Order/Queries/GetAllOrdersQuery.cs:29-34 β 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 `src/Services/Order/Core/Order.Application/Features/Order/Queries/GetAllMyOrdersQuery.cs:30` 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 (8 lines × 2) src/Shared/Common/Extensions/StringExtension.cs:22β src/Shared/Common/Extensions/StringExtension.cs:22-29 | src/Shared/Common/Extensions/StringExtension.cs:41-48 β 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Factories/DatabaseProviderFactory.cs:17β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Factories/DatabaseProviderFactory.cs:17-24 | src/Services/Order/Worker/Order.Woker.Outbox/Factories/DatabaseProviderFactory.cs:17-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 (8 lines × 2) src/Services/Report/Core/Report.Infrastructure/Repositories/OrderGrowthLineChartRepository.cs:36β src/Services/Report/Core/Report.Infrastructure/Repositories/OrderGrowthLineChartRepository.cs:36-43 | src/Services/Report/Core/Report.Infrastructure/Repositories/OrderGrowthLineChartRepository.cs:47-54 β 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 `src/Services/Report/Core/Report.Infrastructure/Repositories/OrderGrowthLineChartRepository.cs:36` 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 × 2) src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationCommittedDomainEventHandler.cs:34β src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationCommittedDomainEventHandler.cs:34-40 | src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationExpiredDomainEventHandler.cs:37-43 β 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 `src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationCommittedDomainEventHandler.cs:34` 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 × 2) REDACTED:22β REDACTED:22-28 | REDACTED:22-28 β before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) src/Services/Order/Core/Order.Application/Features/Order/Queries/GetAllMyOrdersQuery.cs:24β src/Services/Order/Core/Order.Application/Features/Order/Queries/GetAllMyOrdersQuery.cs:24-30 | src/Services/Order/Core/Order.Application/Features/Order/Queries/GetMyOrdersQuery.cs:26-33 β 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 `src/Services/Order/Core/Order.Application/Features/Order/Queries/GetAllMyOrdersQuery.cs:24` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `query` to `GetAllMyOrdersQuery` in one and `GetMyOrdersQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH β their common supertype where they have one, or a new abstraction over them where they do not β and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/CreateInventoryItemCommand.cs:57β src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/CreateInventoryItemCommand.cs:57-61 | src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/UpdateInventoryItemCommand.cs:61-65 β 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/UpdateInventoryItemCommand.cs:60` calls `FirstOrDefaultAsync`, `NotFoundException` and `src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/CreateInventoryItemCommand.cs:57` does not β after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:41β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:41-45 | src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs:41-45 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 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 `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:41` 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 (5 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/DatabaseExtentions.cs:19β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/DatabaseExtentions.cs:19-23 | src/Services/Order/Core/Order.Infrastructure/Data/Extensions/DatabaseExtentions.cs:16-20 β 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.
DM7 Β· Repository granularityΒ· Repository for a non-root entity Β· Γ3
Repository for a non-root entity: InventoryHistoryRepository β InventoryHistoryEntity src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/InventoryHistoryRepository.cs:11β `InventoryHistoryRepository` is a repository over `InventoryHistoryEntity`, 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 `InventoryHistoryEntity` through its owning aggregate instead.
Repository for a non-root entity: LocationRepository β LocationEntity src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/LocationRepository.cs:11β `LocationRepository` is a repository over `LocationEntity`, 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 `LocationEntity` through its owning aggregate instead.
Repository for a non-root entity: IOrderItemRepository β OrderItemEntity src/Services/Order/Core/Order.Domain/Repositories/IOrderItemRepository.cs:9β `IOrderItemRepository` is a repository over `OrderItemEntity`, 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 `OrderItemEntity` through its owning aggregate instead.
X20 Β· Mistyped argument guardΒ· Argument guard throws the exception its own condition disproves Β· Γ3
Argument guard throws the exception its own condition disproves src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs:21β The guard on line 21 rejects `location` and line 21 reports that rejection as `ArgumentNullException` β but the condition's own test `string.IsNullOrWhiteSpace(location)` is true of a value that is NOT null: it is satisfied by an EMPTY `location`, and on that path `location` 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 this 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` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs:42β The guard on line 42 rejects `location` and line 42 reports that rejection as `ArgumentNullException` β but the condition's own test `string.IsNullOrWhiteSpace(location)` is true of a value that is NOT null: it is satisfied by an EMPTY `location`, and on that path `location` 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 this 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` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Services/Inventory/Core/Inventory.Domain/ValueObjects/Product.cs:24β The guard on line 24 rejects `name` and line 24 reports that rejection as `ArgumentNullException` β but the condition's own test `string.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` 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 this 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` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
AC3 Β· Page structureΒ· Heading level jumps from h1 to h5 Β· Γ2
Heading level jumps from h1 to h5 src/Apps/App.Store/src/components/banner/BannerSection3.jsx:49β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h1 to h5 src/Apps/App.Store/src/components/banner/BannerSection8.jsx:48β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
AC3 Β· Page structureΒ· Heading level jumps from h1 to h3 Β· Γ2
Heading level jumps from h1 to h3 src/Apps/App.Store/src/components/banner/BannerSection5.jsx:29β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h1 to h3 src/Apps/App.Store/src/components/banner/BannerSection5.jsx:44β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
AC3 Β· Page structureΒ· Heading level jumps from h2 to h5 Β· Γ2
Heading level jumps from h2 to h5 src/Apps/App.Store/src/components/category/CategorySection.jsx:16β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Heading level jumps from h2 to h5 src/Apps/App.Store/src/components/category/CategorySection2.jsx:34β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
Low contrast colour pair (2.8:1) src/Apps/App.Store/src/components/product/ProductDetailTextSection.jsx:72β The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair (2.8:1) src/Apps/App.Store/src/components/shop/ProductContainer.jsx:50β The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
keycloakService.getUserInfo (cyclomatic 31) src/Apps/App.Admin/src/services/keycloakService.js:266β keycloakService.getUserInfo has cyclomatic complexity 31 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
keycloakService.getUserInfo (cyclomatic 31) src/Apps/App.Store/src/services/keycloakService.js:380β keycloakService.getUserInfo has cyclomatic complexity 31 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D17 Β· Explicit DebtΒ· Whole file has no live code Β· Γ2
Whole file has no live code β 4 debt markers inside it src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:24β 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 4 debt markers (4 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 4 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 β 1 debt marker inside it src/Services/Report/Core/Report.Infrastructure/Services/CatalogGrpcService.cs:48β 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 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 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.)
getUserInfo (cognitive 31) src/Apps/App.Admin/src/services/keycloakService.js:266β getUserInfo has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 18, if/else 5 (6 pts), ternaries 2 (5 pts), error handling 1 (2 pts) (nesting depth added 5). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
getUserInfo (cognitive 31) src/Apps/App.Store/src/services/keycloakService.js:380β getUserInfo has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 18, if/else 5 (6 pts), ternaries 2 (5 pts), error handling 1 (2 pts) (nesting depth added 5). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D4 Β· Code DuplicationΒ· Edited copy of a member (50 corresponding lines) Β· Γ2
Edited copy of a member (50 corresponding lines) src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:57β src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:57-106 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:57-106 β These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (50 corresponding lines) src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:55β src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:55-104 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:55-104 β These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (29 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17-45 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17-45 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs` and `src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:50β src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:50-78 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductsQuery.cs:51-79 β 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 `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:50` 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 (23β24 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:45β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:45-68 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryReservationConfiguration.cs:54-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 `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<InventoryItemEntity>` in one and `EntityTypeBuilder<InventoryReservationEntity>` 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryReservationConfiguration.cs:78` calls `HasIndex` and `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:69` 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 (23β24 lines × 2) src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:51β src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:51-74 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/Processors/OutboxProcessor.cs:50-72 β before extracting anything, compare `src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs` and `src/Services/Catalog/Worker/Catalog.Woker.Outbox/Processors/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 103 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 `src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:65β src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:65-86 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:63-84 β before extracting anything, compare `src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.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 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. 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 (22 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:65β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:65-86 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:63-84 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs` and `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.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 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. 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 (20 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:53β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:53-72 | src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs:53-72 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 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 (20 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:17β src/Services/Inventory/Core/Inventory.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:17-36 | src/Services/Report/Core/Report.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:17-38 β 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 (15 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:70β src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:70-84 | src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:112-126 β 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 `src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.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 (15 lines × 2) src/Services/Basket/Core/Basket.Application/Repositories/IOutboxRepository.cs:9β src/Services/Basket/Core/Basket.Application/Repositories/IOutboxRepository.cs:9-23 | src/Services/Catalog/Core/Catalog.Application/Repositories/IOutboxRepository.cs:9-23 β 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 `src/Services/Basket/Core/Basket.Application/Repositories/IOutboxRepository.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:19β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:19-30 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:19-30 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:19-30 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:19-30 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs` and `src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<InboxMessageEntity>` in one and `EntityTypeBuilder<OutboxMessageEntity>` 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 (12 lines × 4) src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:41β src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:41-52 | src/Services/Discount/Core/Discount.Infrastructure/DependencyInjection.cs:28-39 | src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:50-61 | src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs:44-55 β before extracting anything, compare `src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs` and `src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) src/Services/Basket/Core/Basket.Application/Services/ICatalogGrpcService.cs:9β src/Services/Basket/Core/Basket.Application/Services/ICatalogGrpcService.cs:9-17 | src/Services/Order/Core/Order.Application/Services/ICatalogGrpcService.cs:9-17 β 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 `src/Services/Basket/Core/Basket.Application/Services/ICatalogGrpcService.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/CreateCouponCommand.cs:57β src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/CreateCouponCommand.cs:57-65 | src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/UpdateValidityPeriodCommand.cs:30-38 β 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.
DM12 Β· Ambient inputs in the domainΒ· Domain type reads a global random source Β· Γ2
Domain type reads a global random source: DeliveryEntity src/Services/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:102β `DeliveryEntity` draws from `Random.Shared` inside `RaiseError`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter β an injected `Random`, a seeded generator, or the already-chosen value β so a caller (and a test) can decide it.
Domain type reads a global random source: InboxMessageEntity src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.cs:79β `InboxMessageEntity` draws from `Random.Shared` inside `RecordFailedAttempt`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter β an injected `Random`, a seeded generator, or the already-chosen value β so a caller (and a test) can decide it.
Temporal coupling in handler: UpsertedProductIntegrationEventHandler.Consume src/Services/Notification/Worker/Notification.Worker.Consumer/EventHandlers/Integrations/UpsertedProductIntegrationEventHandler.cs:29β `UpsertedProductIntegrationEventHandler.Consume` makes a synchronous remote call (an HTTP call: `IKeycloakApi.GetAccessTokenAsync` is declared `[Post]`, a generated REST client via `IKeycloakService.GetUsersByRoleAsync`) while handling an event. The handler now depends, in real time, on another service being up and fast β the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: OrderCreatedIntegrationEventHandler.Consume src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCreatedIntegrationEventHandler.cs:30β `OrderCreatedIntegrationEventHandler.Consume` makes a synchronous remote call (a gRPC call) while handling an event. The handler now depends, in real time, on another service being up and fast β the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Fake-async β async method never awaits src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/DeletedUnPublishedProductDomainEventHandler.cs:32β `PushToOutboxAsync` 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 src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/UpsertedProductDomainEventHandler.cs:32β `PushToOutboxAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplicated block (103 lines × 2 locations) src/Apps/App.Admin/src/pages/inventory/index.jsx:1505β src/Apps/App.Admin/src/pages/inventory/index.jsx:1505 · src/Apps/App.Admin/src/pages/inventory/index.jsx:1701 β 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 (103 lines × 2 locations) src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:16β src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:16 · src/Apps/App.Admin/src/pages/utility/invoice.jsx:71 β 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 (74 lines × 2 locations) src/Apps/App.Admin/src/components/partials/Table/team-table.jsx:248β src/Apps/App.Admin/src/components/partials/Table/team-table.jsx:248 · src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:199 β the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (74 lines × 2 locations) src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:195β src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:195 · src/Apps/App.Admin/src/pages/utility/invoice.jsx:284 β 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 (73 lines × 2 locations) src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:178β src/Apps/App.Admin/src/components/partials/Table/company-table.jsx:178 · src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:184 β the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (73 lines × 2 locations) src/Apps/App.Admin/src/pages/coupon/index.jsx:588β src/Apps/App.Admin/src/pages/coupon/index.jsx:588 · src/Apps/App.Admin/src/pages/product/index.jsx:439 β 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.
Boundary violation [package:third-party-deep-import] src/Apps/App.Admin/src/components/ui/InputGroup.jsx:4β src/Apps/App.Admin/src/components/ui/InputGroup.jsx:4 imports cleave.js/dist/addons/cleave-phone.us, reaching past a declared dependency's public entry into its build output β that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] src/Apps/App.Admin/src/components/ui/Textinput.jsx:4β src/Apps/App.Admin/src/components/ui/Textinput.jsx:4 imports cleave.js/dist/addons/cleave-phone.us, reaching past a declared dependency's public entry into its build output β that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Complex function getUserInfo (cyclomatic 31, cognitive 31) src/Apps/App.Admin/src/services/keycloakService.js:266β getUserInfo has cyclomatic complexity 31 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side β extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getUserInfo (cyclomatic 31, cognitive 31) src/Apps/App.Store/src/services/keycloakService.js:380β getUserInfo has cyclomatic complexity 31 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side β extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function syncUserInfo (cyclomatic 20, cognitive 25) src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:68β syncUserInfo has cyclomatic complexity 20 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side β extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function syncUserInfo (cyclomatic 20, cognitive 25) src/Apps/App.Store/src/contexts/KeycloakContext.jsx:122β syncUserInfo has cyclomatic complexity 20 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side β extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Dead file (~319 LoC) src/Apps/App.Admin/src/pages/forms/form-wizard/HorizentalWizard.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/forms/form-wizard/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~319 LoC) src/Apps/App.Admin/src/pages/forms/form-wizard/Vertical.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/forms/form-wizard/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~252 LoC) src/Apps/App.Admin/src/pages/components/button.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~252 LoC) src/Apps/App.Admin/src/pages/forms/select/Options.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/forms/select/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~213 LoC) src/Apps/App.Admin/src/pages/app/todo/AddTodo.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/todo/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~213 LoC) src/Apps/App.Admin/src/pages/table/table-basic.jsxβ no import path from any entry point (15 application, 4 tooling, 0 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
AC1 Β· Text alternativesΒ· <video> without a captions track Β· Γ1
<video> without a captions track src/Apps/App.Admin/src/components/ui/VideoPlayer.jsx:12β Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions β accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied β and capture that asset wherever the media enters the product (upload, import or generation).
AC2 Β· Forms & labelsΒ· <Combobox> field component without a label Β· Γ1
<Combobox> field component without a label src/Apps/App.Admin/src/components/partials/header/Tools/SearchModal.jsx:89β This UI-library field component is named only by a placeholder β a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) β labelling each item leaves the set unnamed.
AC2 Β· Forms & labelsΒ· <ComboboxInput> field component without a label Β· Γ1
<ComboboxInput> field component without a label src/Apps/App.Admin/src/components/partials/header/Tools/SearchModal.jsx:96β This UI-library field component is named only by a placeholder β a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) β labelling each item leaves the set unnamed.
AC3 Β· Page structureΒ· Data table has no header cells Β· Γ1
Data table has no header cells src/Apps/App.Admin/src/pages/product/productDetails.jsx:386β A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC3 Β· Page structureΒ· Heading level jumps from h3 to h6 Β· Γ1
Heading level jumps from h3 to h6 src/Apps/App.Store/src/components/contact/ContactSection.jsx:40β Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels β increase by at most one.
AC4 Β· Keyboard semanticsΒ· Anchor without href Β· Γ1
Anchor without href src/Apps/App.Store/src/components/blog/BlogTagFilter.jsx:13β An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Low contrast Tailwind colour pair (2.4:1) src/Apps/App.Admin/src/components/partials/ecommerce/steps/cart-step.jsx:105β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Focus outline removed inline src/Apps/App.Admin/src/pages/app/chat/Chat.jsx:204β <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Low contrast Tailwind colour pair (3.7:1) src/Apps/App.Admin/src/pages/changelog.jsx:117β This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
Low contrast colour pair (3.3:1) src/Apps/App.Store/src/components/product/ProductDetailTextSection.jsx:105β The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them.
Low contrast colour pair in CSS (2.5:1) src/Apps/App.Store/public/assets/scss/sections/_category.scss:1107β `&:hover` sets color: #ffffff on background-color: #FF7C7C β 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.0:1) src/Apps/App.Store/public/assets/scss/sections/_featured-products.scss:1566β `span` sets color: #fff on background-color: #FFA239 β 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.3:1) src/Apps/App.Store/public/assets/scss/pages/_shop.scss:275β `&.active` sets color: #fff on background-color: #B8860B β 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 Β· A11y enforcementΒ· Accessibility enforcement below the top rung Β· Γ1
Accessibility enforcement below the top rung src/Apps/App.Store/package.json:37β 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 584 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.
C1 Β· Data ProtectionΒ· No data-protection/encryption Β· Γ1
No data-protection/encryption β No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found β sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
index.InventoryPage (cyclomatic 171) src/Apps/App.Admin/src/pages/inventory/index.jsx:53β index.InventoryPage has cyclomatic complexity 171 (threshold 15). Of this number, 48 points are the body's own statements and 123 belong to 26 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.CouponPage (cyclomatic 128) src/Apps/App.Admin/src/pages/coupon/index.jsx:36β index.CouponPage has cyclomatic complexity 128 (threshold 15). Of this number, 40 points are the body's own statements and 88 belong to 18 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
details.OrderDetails (cyclomatic 93) src/Apps/App.Admin/src/pages/orders/details.jsx:63β details.OrderDetails has cyclomatic complexity 93 (threshold 15). Of this number, 63 points are the body's own statements and 30 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.Orders (cyclomatic 87) src/Apps/App.Admin/src/pages/orders/index.jsx:88β index.Orders has cyclomatic complexity 87 (threshold 15). Of this number, 20 points are the body's own statements and 67 belong to 21 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
productDetails.ProductDetails (cyclomatic 72) src/Apps/App.Admin/src/pages/product/productDetails.jsx:35β productDetails.ProductDetails has cyclomatic complexity 72 (threshold 15). Of this number, 44 points are the body's own statements and 28 belong to 8 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.CategoryPage (cyclomatic 64) src/Apps/App.Admin/src/pages/category/index.jsx:36β index.CategoryPage has cyclomatic complexity 64 (threshold 15). Of this number, 20 points are the body's own statements and 44 belong to 15 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CheckoutSection.CheckoutSection (cyclomatic 58) src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:15β CheckoutSection.CheckoutSection has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 3 of the 58 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 163, handleSubmit, handleApplyCoupon). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.Ecommerce (cyclomatic 55) src/Apps/App.Admin/src/pages/product/index.jsx:43β index.Ecommerce has cyclomatic complexity 55 (threshold 15). Of this number, 23 points are the body's own statements and 32 belong to 13 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
edit.EditOrder (cyclomatic 53) src/Apps/App.Admin/src/pages/orders/edit.jsx:18β edit.EditOrder has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 12 of the 53 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 53, 139, 30, β¦). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
KeycloakContext.KeycloakProvider (cyclomatic 51) src/Apps/App.Store/src/contexts/KeycloakContext.jsx:15β KeycloakContext.KeycloakProvider has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 2 of the 51 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 44, a function literal at line 122, a function literal at line 169, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
edit-coupon.EditCoupon (cyclomatic 48) src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:16β edit-coupon.EditCoupon has cyclomatic complexity 48 (threshold 15). Of this number, 20 points are the body's own statements and 28 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
create-coupon.CreateCoupon (cyclomatic 46) src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:15β create-coupon.CreateCoupon has cyclomatic complexity 46 (threshold 15). Of this number, 25 points are the body's own statements and 21 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
create-product.CreateProduct (cyclomatic 42) src/Apps/App.Admin/src/pages/product/create-product.jsx:17β create-product.CreateProduct has cyclomatic complexity 42 (threshold 15). Of this number, 16 points are the body's own statements and 26 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
InputGroup.InputGroup (cyclomatic 41) src/Apps/App.Admin/src/components/ui/InputGroup.jsx:6β InputGroup.InputGroup has cyclomatic complexity 41 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Button.Button (cyclomatic 40) src/Apps/App.Admin/src/components/ui/Button.jsx:4β Button.Button has cyclomatic complexity 40 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
KeycloakContext.KeycloakProvider (cyclomatic 38) src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:18β KeycloakContext.KeycloakProvider has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 2 of the 38 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 68, 28, 117, β¦). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.BrandPage (cyclomatic 38) src/Apps/App.Admin/src/pages/brand/index.jsx:35β index.BrandPage has cyclomatic complexity 38 (threshold 15). Of this number, 16 points are the body's own statements and 22 belong to 10 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Modal.Modal (cyclomatic 35) src/Apps/App.Admin/src/components/ui/Modal.jsx:5β Modal.Modal has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OrderDetailModal.OrderDetailModal (cyclomatic 34) src/Apps/App.Store/src/components/modal/OrderDetailModal.jsx:17β OrderDetailModal.OrderDetailModal has cyclomatic complexity 34 (threshold 15). Of this number, 23 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Notification.Notification (cyclomatic 31) src/Apps/App.Admin/src/components/partials/header/Tools/Notification.jsx:12β Notification.Notification has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 30, a function literal at line 173, formatTimeAgo, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.NotificationPage (cyclomatic 31) src/Apps/App.Admin/src/pages/notification/index.jsx:53β index.NotificationPage has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 12 function items inside it that branch (formatTimeAgo, handleNotificationClick, handleMarkSelectedAsRead, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Textinput.Textinput (cyclomatic 29) src/Apps/App.Admin/src/components/ui/Textinput.jsx:5β Textinput.Textinput has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.Header (cyclomatic 28) src/Apps/App.Admin/src/components/partials/header/index.jsx:23β index.Header has cyclomatic complexity 28 (threshold 15). Of this number, 20 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ProductDetailTextSection.ProductDetailTextSection (cyclomatic 27) src/Apps/App.Store/src/components/product/ProductDetailTextSection.jsx:4β ProductDetailTextSection.ProductDetailTextSection has cyclomatic complexity 27 (threshold 15). Of this number, 15 points are the body's own statements and 12 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
create.CreateOrder (cyclomatic 26) src/Apps/App.Admin/src/pages/orders/create.jsx:17β create.CreateOrder has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 82, 27, 34, β¦). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
edit-product.EditProduct::getInitialValues (cyclomatic 24) src/Apps/App.Admin/src/pages/product/edit-product.jsx:144β edit-product.EditProduct::getInitialValues has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (edit-product.EditProduct) has the same decision points, in the same order, at the same nesting depths β so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
index.EmailPage (cyclomatic 23) src/Apps/App.Admin/src/pages/app/email/index.jsx:24β index.EmailPage has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 39, 63, 33). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FarzaaContext.FarzaaContextProvider::fetchProducts (cyclomatic 23) src/Apps/App.Store/src/context/FarzaaContext.jsx:244β FarzaaContext.FarzaaContextProvider::fetchProducts has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Layout.Layout (cyclomatic 22) src/Apps/App.Admin/src/layout/Layout.jsx:21β Layout.Layout has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Select.Select (cyclomatic 22) src/Apps/App.Admin/src/components/ui/Select.jsx:3β Select.Select has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Navmenu.Navmenu (cyclomatic 21) src/Apps/App.Admin/src/components/partials/sidebar/Navmenu.jsx:10β Navmenu.Navmenu has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 80, a function literal at line 45, a function literal at line 51, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CustomExceptionHandler.TryHandleAsync (cyclomatic 20) src/Shared/BuildingBlocks/Exceptions/Handler/CustomExceptionHandler.cs:23β CustomExceptionHandler.TryHandleAsync has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.TodoPage (cyclomatic 20) src/Apps/App.Admin/src/pages/app/todo/index.jsx:71β index.TodoPage has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 88, 110, 81). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ProductDetailAction.ProductDetailAction (cyclomatic 18) src/Apps/App.Store/src/components/product/ProductDetailAction.jsx:3β ProductDetailAction.ProductDetailAction has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
initKeycloak (cyclomatic 18) src/Apps/App.Store/src/services/keycloakService.js:92β initKeycloak has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 190, getConsistentRedirectUri, a function literal at line 225, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
edit-product.EditProduct (cyclomatic 17) src/Apps/App.Admin/src/pages/product/edit-product.jsx:17β edit-product.EditProduct has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (edit-product.EditProduct::getInitialValues) has the same decision points, in the same order, at the same nesting depths β so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
edit-inventory.EditInventory (cyclomatic 17) src/Apps/App.Admin/src/pages/inventory/edit-inventory.jsx:101β edit-inventory.EditInventory has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 127). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Textarea.Textarea (cyclomatic 17) src/Apps/App.Admin/src/components/ui/Textarea.jsx:3β Textarea.Textarea has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HorizentalWizard.FormWizard (cyclomatic 17) src/Apps/App.Admin/src/pages/forms/form-wizard/HorizentalWizard.jsx:65β HorizentalWizard.FormWizard has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Vertical.FormWizard (cyclomatic 17) src/Apps/App.Admin/src/pages/forms/form-wizard/Vertical.jsx:65β Vertical.FormWizard has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
NotificationsMain.NotificationsMain (cyclomatic 16) src/Apps/App.Store/src/components/main/NotificationsMain.jsx:7β NotificationsMain.NotificationsMain has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 113, handleNotificationClick, fetchNotifications, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TodoComment src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCreatedIntegrationEventHandler.cs:131β // TODO: Publish InventoryReservationFailedIntegrationEvent β 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.
index.InventoryPage (cognitive 163) src/Apps/App.Admin/src/pages/inventory/index.jsx:53β index.InventoryPage has cognitive complexity 163 (threshold 15). Drivers by points: boolean chains 73, ternaries 45 (54 pts), if/else 22 (26 pts), error handling 10 (nesting depth added 13). Of this number, 47 points are the body's own statements and 116 belong to 26 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth β checks laid out side by side rather than stacked β so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
index.CouponPage (cognitive 115) src/Apps/App.Admin/src/pages/coupon/index.jsx:36β index.CouponPage has cognitive complexity 115 (threshold 15). Drivers by points: boolean chains 56, ternaries 26 (35 pts), if/else 16 (18 pts), error handling 6 (nesting depth added 11). Of this number, 28 points are the body's own statements and 87 belong to 18 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.Orders (cognitive 90) src/Apps/App.Admin/src/pages/orders/index.jsx:88β index.Orders has cognitive complexity 90 (threshold 15). Drivers by points: boolean chains 38, ternaries 24 (31 pts), if/else 17 (18 pts), error handling 3 (nesting depth added 8). Of this number, 19 points are the body's own statements and 71 belong to 21 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth β checks laid out side by side rather than stacked β so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
details.OrderDetails (cognitive 76) src/Apps/App.Admin/src/pages/orders/details.jsx:63β details.OrderDetails has cognitive complexity 76 (threshold 15). Drivers by points: boolean chains 56, if/else 9, ternaries 8 (9 pts), error handling 2 (nesting depth added 1). Of this number, 50 points are the body's own statements and 26 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
productDetails.ProductDetails (cognitive 70) src/Apps/App.Admin/src/pages/product/productDetails.jsx:35β productDetails.ProductDetails has cognitive complexity 70 (threshold 15). Drivers by points: boolean chains 33, if/else 16 (19 pts), ternaries 14 (16 pts), error handling 2 (nesting depth added 5). Of this number, 40 points are the body's own statements and 30 belong to 8 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth β checks laid out side by side rather than stacked β so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
index.CategoryPage (cognitive 61) src/Apps/App.Admin/src/pages/category/index.jsx:36β index.CategoryPage has cognitive complexity 61 (threshold 15). Drivers by points: boolean chains 29, ternaries 15 (17 pts), if/else 10 (11 pts), error handling 4 (nesting depth added 3). Of this number, 19 points are the body's own statements and 42 belong to 15 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.Ecommerce (cognitive 58) src/Apps/App.Admin/src/pages/product/index.jsx:43β index.Ecommerce has cognitive complexity 58 (threshold 15). Drivers by points: ternaries 31 (37 pts), boolean chains 10, if/else 8, error handling 3 (nesting depth added 6). Of this number, 25 points are the body's own statements and 33 belong to 13 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth β checks laid out side by side rather than stacked β so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
KeycloakContext.KeycloakProvider (cognitive 58) src/Apps/App.Store/src/contexts/KeycloakContext.jsx:15β KeycloakContext.KeycloakProvider has cognitive complexity 58 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 18, error handling 3 (6 pts), ternaries 1 (5 pts), loops 2 (4 pts) (nesting depth added 20). Most of this is not in the body itself: 1 of the 58 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 122, a function literal at line 44, isProcessingCallback, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Modal.Modal (cognitive 51) src/Apps/App.Admin/src/components/ui/Modal.jsx:5β Modal.Modal has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 24 (47 pts), boolean chains 4 (nesting depth added 23). 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.
edit.EditOrder (cognitive 46) src/Apps/App.Admin/src/pages/orders/edit.jsx:18β edit.EditOrder has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 34, if/else 7 (8 pts), error handling 3, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 11 of the 46 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 53, 139, 30, β¦). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CheckoutSection.CheckoutSection (cognitive 46) src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:15β CheckoutSection.CheckoutSection has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 27, ternaries 13 (14 pts), if/else 3, error handling 2 (nesting depth added 1). Most of this is not in the body itself: 2 of the 46 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 163, handleSubmit, handleApplyCoupon). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
edit-coupon.EditCoupon (cognitive 44) src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:16β edit-coupon.EditCoupon has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 22, ternaries 14, if/else 6, error handling 2. Of this number, 17 points are the body's own statements and 27 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
KeycloakContext.KeycloakProvider (cognitive 44) src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:18β KeycloakContext.KeycloakProvider has cognitive complexity 44 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 13, error handling 3 (6 pts), ternaries 1 (5 pts), loops 1 (2 pts) (nesting depth added 17). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 68, 28, 181, β¦). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
create-coupon.CreateCoupon (cognitive 41) src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:15β create-coupon.CreateCoupon has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 20, ternaries 14, if/else 6, error handling 1. Of this number, 22 points are the body's own statements and 19 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
create-product.CreateProduct (cognitive 39) src/Apps/App.Admin/src/pages/product/create-product.jsx:17β create-product.CreateProduct has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 18, if/else 10, ternaries 8, error handling 3. Most of this is not in the body itself: 15 of the 39 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 136, a function literal at line 33, a function literal at line 54, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Notification.Notification (cognitive 39) src/Apps/App.Admin/src/components/partials/header/Tools/Notification.jsx:12β Notification.Notification has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 6 (15 pts), if/else 12, boolean chains 10, error handling 2 (nesting depth added 9). Most of this is not in the body itself: 6 of the 39 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 30, a function literal at line 173, a function literal at line 62, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.BrandPage (cognitive 36) src/Apps/App.Admin/src/pages/brand/index.jsx:35β index.BrandPage has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 14 (16 pts), boolean chains 11, if/else 5, error handling 4 (nesting depth added 2). Of this number, 16 points are the body's own statements and 20 belong to 10 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth β checks laid out side by side rather than stacked β so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
index.NotificationPage (cognitive 34) src/Apps/App.Admin/src/pages/notification/index.jsx:53β index.NotificationPage has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 16 (19 pts), if/else 7, boolean chains 4, error handling 3 (4 pts) (nesting depth added 4). Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 12 function items inside it that branch (formatTimeAgo, handleNotificationClick, a function literal at line 333, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
OrderDetailModal.OrderDetailModal (cognitive 34) src/Apps/App.Store/src/components/modal/OrderDetailModal.jsx:17β OrderDetailModal.OrderDetailModal has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 23, ternaries 3 (6 pts), if/else 4, error handling 1 (nesting depth added 3). Of this number, 23 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GetAllAvailableProductsQueryHandler.Handle (cognitive 30) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:21β GetAllAvailableProductsQueryHandler.Handle has cognitive complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GetAllProductsQueryHandler.Handle (cognitive 29) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:21β GetAllProductsQueryHandler.Handle has cognitive complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
GetProductsQueryHandler.Handle (cognitive 29) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:24β GetProductsQueryHandler.Handle has cognitive complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
GetPublishProductsQueryHandler.Handle (cognitive 28) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductsQuery.cs:24β GetPublishProductsQueryHandler.Handle has cognitive complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InputGroup.InputGroup (cognitive 26) src/Apps/App.Admin/src/components/ui/InputGroup.jsx:6β InputGroup.InputGroup has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 17, ternaries 9. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
create.CreateOrder (cognitive 24) src/Apps/App.Admin/src/pages/orders/create.jsx:17β create.CreateOrder has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 18, if/else 3, error handling 2, ternaries 1. Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 82, 27, 34, β¦). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
NotificationsMain.NotificationsMain (cognitive 24) src/Apps/App.Store/src/components/main/NotificationsMain.jsx:7β NotificationsMain.NotificationsMain has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 6, error handling 3 (4 pts), boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 5 function items inside it that branch (handleNotificationClick, a function literal at line 113, fetchNotifications, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Navmenu.Navmenu (cognitive 22) src/Apps/App.Admin/src/components/partials/sidebar/Navmenu.jsx:10β Navmenu.Navmenu has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, ternaries 3 (nesting depth added 4). None of this is in the body itself: all 22 points belong to 8 function items inside it that branch (a function literal at line 80, toggleSubmenu, toggleMultiMenu, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
edit-product.EditProduct::getInitialValues (cognitive 22) src/Apps/App.Admin/src/pages/product/edit-product.jsx:144β edit-product.EditProduct::getInitialValues has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, ternaries 5, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (edit-product.EditProduct) has the same decision points, in the same order, at the same nesting depths β so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ProductDetailTextSection.ProductDetailTextSection (cognitive 22) src/Apps/App.Store/src/components/product/ProductDetailTextSection.jsx:4β ProductDetailTextSection.ProductDetailTextSection has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 15, if/else 5 (6 pts), ternaries 1 (nesting depth added 1). Of this number, 13 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.Header (cognitive 21) src/Apps/App.Admin/src/components/partials/header/index.jsx:23β index.Header has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 15, if/else 3, ternaries 2, match/switch 1. Of this number, 15 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
initKeycloak (cognitive 21) src/Apps/App.Store/src/services/keycloakService.js:92β initKeycloak has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, error handling 3 (4 pts) (nesting depth added 3). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 190, getConsistentRedirectUri, a function literal at line 225, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.EmailPage (cognitive 20) src/Apps/App.Admin/src/pages/app/email/index.jsx:24β index.EmailPage has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10, boolean chains 8, ternaries 2. Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 39, 63, 33). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FarzaaContext.FarzaaContextProvider::fetchProducts (cognitive 19) src/Apps/App.Store/src/context/FarzaaContext.jsx:244β FarzaaContext.FarzaaContextProvider::fetchProducts has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 10, boolean chains 6, error handling 1, if/else 1, match/switch 1. To reduce it, split the body: this score is breadth rather than depth β many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Layout.Layout (cognitive 18) src/Apps/App.Admin/src/layout/Layout.jsx:21β Layout.Layout has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 6 (7 pts), ternaries 4 (nesting depth added 1). Of this number, 9 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth β many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Button.Button (cognitive 18) src/Apps/App.Admin/src/components/ui/Button.jsx:4β Button.Button has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 18. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Textinput.Textinput (cognitive 18) src/Apps/App.Admin/src/components/ui/Textinput.jsx:5β Textinput.Textinput has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 14, ternaries 4. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.TodoPage (cognitive 18) src/Apps/App.Admin/src/pages/app/todo/index.jsx:71β index.TodoPage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 2. Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 88, 110, 81). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useMenuTranslation (cognitive 18) src/Apps/App.Admin/src/hooks/useMenuTranslation.js:126β useMenuTranslation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 18 points belong to 7 function items inside it that branch (a function literal at line 135, a function literal at line 146, a function literal at line 171, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
edit-inventory.EditInventory (cognitive 17) src/Apps/App.Admin/src/pages/inventory/edit-inventory.jsx:101β edit-inventory.EditInventory has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 13, ternaries 2 (3 pts), if/else 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 127). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ProductContainer.ProductContainer (cognitive 17) src/Apps/App.Store/src/components/shop/ProductContainer.jsx:7β ProductContainer.ProductContainer has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (13 pts), boolean chains 4 (nesting depth added 7). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 33). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
initKeycloak (cognitive 17) src/Apps/App.Admin/src/services/keycloakService.js:84β initKeycloak has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 1, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 166, a function literal at line 129, onAuthSuccess, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CustomExceptionHandler.TryHandleAsync (cognitive 16) src/Shared/BuildingBlocks/Exceptions/Handler/CustomExceptionHandler.cs:23β CustomExceptionHandler.TryHandleAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth β many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Submenu.Submenu (cognitive 16) src/Apps/App.Admin/src/components/partials/sidebar/Submenu.jsx:7β Submenu.Submenu has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (15 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 17, 66). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
edit-product.EditProduct (cognitive 16) src/Apps/App.Admin/src/pages/product/edit-product.jsx:17β edit-product.EditProduct has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 38, if/else 13, ternaries 13, error handling 4. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (edit-product.EditProduct::getInitialValues) has the same decision points, in the same order, at the same nesting depths β so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Select.Select (cognitive 16) src/Apps/App.Admin/src/components/ui/Select.jsx:3β Select.Select has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, ternaries 7. Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.CalendarPage (cognitive 16) src/Apps/App.Admin/src/pages/app/calendar/index.jsx:22β index.CalendarPage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, ternaries 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (handleClassName, handleCategorySelection, a function literal at line 180, β¦). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MethodTooLong: ProductSeedData.GetAllProducts src/Services/Catalog/Core/Catalog.Infrastructure/Data/ProductSeedData.cs:19β MethodTooLong β GetAllProducts runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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.
D30 Β· Dependency VulnerabilitiesΒ· Medium vulnerability Β· Γ1
D4 Β· Code DuplicationΒ· Edited copy of a member (48 corresponding lines) Β· Γ1
Edited copy of a member (48 corresponding lines) src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:25β src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:25-76 | src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:24-74 β These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below β the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain β factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 Β· Code DuplicationΒ· Members sharing a duplicated core (8 members, 50+ identical tokens) Β· Γ1
Members sharing a duplicated core (8 members, 50+ identical tokens) REDACTED:67β REDACTED:67-96 | REDACTED:64-93 | REDACTED:67-96 | REDACTED:63-92 | REDACTED:62-91 | REDACTED:63-92 | REDACTED:62-91 | REDACTED:71-102 β These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below β it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain β factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 Β· Code DuplicationΒ· Members sharing a duplicated core (6 members, 50+ identical tokens) Β· Γ1
Members sharing a duplicated core (6 members, 50+ identical tokens) src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:24β src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:24-71 | src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:20-50 | src/Services/Discount/Core/Discount.Infrastructure/DependencyInjection.cs:20-57 | src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:26-69 | src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs:20-59 | src/Services/Search/Core/Search.Infrastructure/DependencyInjection.cs:22-54 β 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 (76 lines × 2) src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:23β src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:23-98 | src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs:27-102 β before extracting anything, compare `src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs` and `src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:23` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (58β60 lines × 2) src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:102β src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs:102-161 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/Processors/OutboxProcessor.cs:113-170 β before extracting anything, compare `src/Services/Basket/Worker/Basket.Worker.Outbox/Processors/OutboxProcessor.cs` and `src/Services/Catalog/Worker/Catalog.Woker.Outbox/Processors/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (51 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:79β src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:79-129 | src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs:79-129 β before extracting anything, compare `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs` and `src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 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 (38 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:19β src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:19-56 | src/Services/Order/Core/Order.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:19-56 β before extracting anything, compare `src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs` and `src/Services/Order/Core/Order.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (36 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:45β src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:45-80 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:51-86 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17β33 lines × 3) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:40β src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:40-56 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:38-70 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:45-76 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:40` calls `ToList` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:38` 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 (32 lines × 2) src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:31β src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:31-62 | src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs:25-56 β before extracting anything, compare `src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs` and `src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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 `src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:66` calls `AddRefitClients` and `src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs:58` 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 (31 lines × 3) src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakUser.cs:11β src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakUser.cs:11-41 | src/Services/Notification/Core/Notification.Domain/Models/Externals/Keycloaks/KeycloakUser.cs:11-41 | src/Services/Report/Core/Report.Domain/Models/Externals/Keycloaks/KeycloakUser.cs:11-41 β before extracting anything, compare `src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakUser.cs` and `src/Services/Notification/Core/Notification.Domain/Models/Externals/Keycloaks/KeycloakUser.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 (31 lines × 2) src/Services/Inventory/Core/Inventory.Domain/Repositories/IRepository.cs:9β src/Services/Inventory/Core/Inventory.Domain/Repositories/IRepository.cs:9-39 | src/Services/Order/Core/Order.Domain/Repositories/IRepository.cs:9-39 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Domain/Repositories/IRepository.cs` and `src/Services/Order/Core/Order.Domain/Repositories/IRepository.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Core/Inventory.Domain/Repositories/IRepository.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 3) src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:42β src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:42-70 | src/Services/Inventory/Core/Inventory.Infrastructure/Services/CatalogGrpcService.cs:45-73 | src/Services/Order/Core/Order.Infrastructure/Services/CatalogGrpcService.cs:42-70 β before extracting anything, compare `src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs` and `src/Services/Order/Core/Order.Infrastructure/Services/CatalogGrpcService.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (29 lines × 8) REDACTED:68β REDACTED:68-96 | REDACTED:65-93 | REDACTED:68-96 | REDACTED:64-92 | REDACTED:63-91 | REDACTED:64-92 | REDACTED:63-91 | REDACTED:74-102 β before extracting anything, compare `REDACTED` and `REDACTED` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `REDACTED:74` 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, `REDACTED:72` calls `UseInfrastructure` and `REDACTED:67` 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 (28 lines × 3) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:34β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:34-61 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:34-61 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:34-61 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs` and `src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 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 `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:34` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<OutboxMessageEntity>` in one and `EntityTypeBuilder<InboxMessageEntity>` 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 (27β29 lines × 2) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:7β src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:7-33 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:7-35 β before extracting anything, compare `src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs` and `src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 3) src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:47β src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:47-70 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:48-71 | src/Services/Order/Worker/Order.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:47-70 β before extracting anything, compare `src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs` and `src/Services/Inventory/Worker/Inventory.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.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.
Duplicated block (26 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:22β src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:22-47 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:27-52 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:22` 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 after the matched lines, `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:49` calls `RuleFor`, `NotNull`, `WithMessage` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:53` does not β after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 5) src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakAccessToken.cs:11β src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakAccessToken.cs:11-32 | src/Services/Inventory/Core/Inventory.Application/Models/Responses/Externals/KeycloakAccessTokenResponse.cs:11-32 | src/Services/Notification/Core/Notification.Domain/Models/Externals/Keycloaks/KeycloakAccessToken.cs:11-32 | src/Services/Order/Core/Order.Application/Models/Responses/KeycloakAccessTokenResponse.cs:11-32 | src/Services/Report/Core/Report.Domain/Models/Externals/Keycloaks/KeycloakAccessToken.cs:11-32 β before extracting anything, compare `src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakAccessToken.cs` and `src/Services/Inventory/Core/Inventory.Application/Models/Responses/Externals/KeycloakAccessTokenResponse.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 4) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:25β src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:25-45 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:27-47 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:25-45 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:33-53 β before extracting anything, compare `src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs` and `src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place.
Duplicated block (22β23 lines × 4) src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCancelledIntegrationEventHandler.cs:32β src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCancelledIntegrationEventHandler.cs:32-53 | src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderDeliveredIntegrationEventHandler.cs:32-53 | src/Services/Order/Worker/Order.Worker.Consumer/EventHandlers/Integrations/BasketCheckoutIntegrationEventHandler.cs:33-55 | src/Services/Order/Worker/Order.Worker.Consumer/EventHandlers/Integrations/ReservationExpiredIntegrationEventHandler.cs:33-54 β the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach β a location they all depend on today, or a new shared one if there is none β and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCancelledIntegrationEventHandler.cs:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `context` to `ConsumeContext<OrderCancelledIntegrationEvent>` in one and `ConsumeContext<OrderDeliveredIntegrationEvent>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH β their common supertype where they have one, or a new abstraction over them where they do not β and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 3) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:72β src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:72-76 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductByIdQuery.cs:50-54 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductsQuery.cs:73-77 β the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach β a file they already depend on, or a new one alongside them β and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:72` 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, `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductByIdQuery.cs:56` calls `GetPublishProductByIdResult` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:77` 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 (21 lines × 2) src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9β src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9-29 | src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:9-29 β before extracting anything, compare `src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs` and `src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.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 `src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 5) src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:75β src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:75-93 | src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:75-93 | src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:75-93 | src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.cs:67-85 | src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs:67-85 β before extracting anything, compare `src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs` and `src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 4) src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:77β src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:77-95 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:77-95 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:78-96 | src/Services/Order/Worker/Order.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:77-95 β before extracting anything, compare `src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs` and `src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs` 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 (20 lines × 3) src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/ChangeProductStatusCommand.cs:45β src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/ChangeProductStatusCommand.cs:45-64 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/PublishProductCommand.cs:45-64 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:111-130 β the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach β a file they already depend on, or a new one alongside them β and call it from all 3 call sites, so a change lands once.
Duplicated block (17β19 lines × 5) src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:20β src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:20-38 | src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 | src/Services/Inventory/Core/Inventory.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 | src/Services/Order/Core/Order.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 | src/Services/Report/Core/Report.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs:19-35 β before extracting anything, compare `src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs` and `src/Services/Inventory/Core/Inventory.Infrastructure/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17β18 lines × 3) src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs:49β src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs:49-66 | src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:39-55 | src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs:43-59 β before extracting anything, compare `src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs` and `src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names β the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17β18 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:36β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:36-52 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OrderItemEntityConfiguration.cs:37-54 β 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 `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:36` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names β the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<InventoryItemEntity>` in one and `EntityTypeBuilder<OrderItemEntity>` 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 (15 lines × 5) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryHistoryConfiguration.cs:27β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryHistoryConfiguration.cs:27-41 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:31-45 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryReservationConfiguration.cs:35-49 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OrderEntityConfiguration.cs:37-51 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OrderItemEntityConfiguration.cs:32-46 β the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<InventoryHistoryEntity>` in one and `EntityTypeBuilder<InventoryItemEntity>` 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:47` calls `ComplexProperty` and `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryReservationConfiguration.cs:51` 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 (16 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:31β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:31-46 | src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:31-46 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs` and `src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16β17 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:39β src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:39-54 | src/Services/Discount/Core/Discount.Infrastructure/DependencyInjection.cs:26-42 β 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 `src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:39` 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 (15β16 lines × 2) src/Services/Report/Core/Report.Infrastructure/Data/Extensions/DatabaseExtentions.cs:65β src/Services/Report/Core/Report.Infrastructure/Data/Extensions/DatabaseExtentions.cs:65-80 | src/Services/Report/Core/Report.Infrastructure/Repositories/DashboardTotalRepository.cs:40-54 β 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 `src/Services/Report/Core/Report.Infrastructure/Data/Extensions/DatabaseExtentions.cs:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand β widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (15 lines × 4) src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs:10β src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs:10-24 | src/Services/Discount/Core/Discount.Domain/Abstractions/Entity.cs:10-24 | src/Services/Notification/Core/Notification.Domain/Abstractions/Entity.cs:10-24 | src/Services/Report/Core/Report.Domain/Abstractions/Entity.cs:10-24 β before extracting anything, compare `src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs` and `src/Services/Discount/Core/Discount.Domain/Abstractions/Entity.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Basket/Core/Basket.Domain/Abstractions/Entity.cs:10` 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β15 lines × 3) src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:24β src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:24-32 | src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:20-34 | src/Services/Search/Core/Search.Infrastructure/DependencyInjection.cs:22-30 β the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach β a location they all depend on today, or a new shared one if there is none β and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:24` 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β15 lines × 2) src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:111β src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:111-125 | src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs:123-135 β before extracting anything, compare `src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs` and `src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (13β14 lines × 3) src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs:26β src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs:26-39 | src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:21-33 | src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs:25-37 β before extracting anything, compare `src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs` and `src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs:26` 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs:39` calls `WithMessage`, `MaximumLength` and `src/Services/Order/Core/Order.Application/Features/Order/Commands/CreateOrderCommand.cs:33` 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 (12β14 lines × 2) src/Services/Basket/Core/Basket.Application/Dtos/Baskets/BasketCheckoutAddressDto.cs:4β src/Services/Basket/Core/Basket.Application/Dtos/Baskets/BasketCheckoutAddressDto.cs:4-17 | src/Shared/EventSourcing/Events/Baskets/BasketCheckoutIntegrationEvent.cs:32-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 `src/Services/Basket/Core/Basket.Application/Dtos/Baskets/BasketCheckoutAddressDto.cs:4` 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 lines × 8) src/Services/Basket/Core/Basket.Application/Dtos/Abstractions/EntityDto.cs:3β src/Services/Basket/Core/Basket.Application/Dtos/Abstractions/EntityDto.cs:3-15 | src/Services/Catalog/Core/Catalog.Application/Dtos/Abstractions/EntityDto.cs:3-15 | src/Services/Discount/Core/Discount.Application/Dtos/Abstractions/EntityDto.cs:3-15 | src/Services/Inventory/Core/Inventory.Application/Dtos/Abstractions/EntityDto.cs:3-15 | src/Services/Notification/Core/Notification.Application/Dtos/Abstractions/EntityDto.cs:3-15 | src/Services/Order/Core/Order.Application/Dtos/Abstractions/EntityDto.cs:3-15 | src/Services/Report/Core/Report.Application/Dtos/Abstractions/EntityDto.cs:3-15 | src/Services/Search/Core/Search.Application/Dtos/Abstractions/EntityDto.cs:3-15 β before extracting anything, compare `src/Services/Basket/Core/Basket.Application/Dtos/Abstractions/EntityDto.cs` and `src/Services/Catalog/Core/Catalog.Application/Dtos/Abstractions/EntityDto.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 `src/Services/Basket/Core/Basket.Application/Dtos/Abstractions/EntityDto.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 (12 lines × 5) src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:25β src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:25-36 | src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:27-38 | src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:34-45 | src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs:28-39 | src/Services/Search/Core/Search.Infrastructure/DependencyInjection.cs:23-34 β before extracting anything, compare `src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs` and `src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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 `src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.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 (12 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:61β src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:61-72 | src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:60-71 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs` and `src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:72` calls `AddRefitClients` and `src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:71` 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 (9 lines × 3) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:26β src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:26-34 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:26-34 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:30-38 β before extracting anything, compare `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together β extracting one helper per block leaves the fork in place. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:40` calls `CountAsync` and `src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:36` 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 (11 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Category/Commands/CreateCategoryCommand.cs:58β src/Services/Catalog/Core/Catalog.Application/Features/Category/Commands/CreateCategoryCommand.cs:58-68 | src/Services/Catalog/Core/Catalog.Application/Features/Category/Commands/UpdateCategoryCommand.cs:70-80 β 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 `src/Services/Catalog/Core/Catalog.Application/Features/Category/Commands/CreateCategoryCommand.cs:58` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `CreateCategoryCommand` in one and `UpdateCategoryCommand` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH β their common supertype where they have one, or a new abstraction over them where they do not β and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 4) src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:35β src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:35-39 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:35-39 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:36-40 | src/Services/Order/Worker/Order.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:35-39 β before extracting anything, compare `src/Services/Basket/Worker/Basket.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs` and `src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs` 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 (80 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/Repository.cs:29β src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/Repository.cs:29-108 | src/Services/Order/Core/Order.Infrastructure/Repositories/Repository.cs:29-108 β before extracting anything, compare `src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/Repository.cs` and `src/Services/Order/Core/Order.Infrastructure/Repositories/Repository.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:16β src/Services/Inventory/Core/Inventory.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:16-36 | src/Services/Order/Core/Order.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:15-32 β the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach β a location they all depend on today, or a new shared one if there is none β and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 8) src/Services/Basket/Core/Basket.Application/DependencyInjection.cs:18β src/Services/Basket/Core/Basket.Application/DependencyInjection.cs:18-33 | src/Services/Catalog/Core/Catalog.Application/DependencyInjection.cs:18-33 | src/Services/Discount/Core/Discount.Application/DependencyInjection.cs:18-33 | src/Services/Inventory/Core/Inventory.Application/DependencyInjection.cs:18-33 | src/Services/Notification/Core/Notification.Application/DependencyInjection.cs:18-31 | src/Services/Order/Core/Order.Application/DependencyInjection.cs:18-32 | src/Services/Report/Core/Report.Application/DependencyInjection.cs:18-31 | src/Services/Search/Core/Search.Application/DependencyInjection.cs:18-31 β before extracting anything, compare `src/Services/Basket/Core/Basket.Application/DependencyInjection.cs` and `src/Services/Catalog/Core/Catalog.Application/DependencyInjection.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it β treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (40 lines × 5) REDACTED:23β REDACTED:23-64 | REDACTED:23-64 | REDACTED:21-60 | REDACTED:21-60 | REDACTED:25-68 β before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 97% 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. β These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:72` calls `UseInfrastructure` and `REDACTED:68` does not β after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) src/Services/Basket/Worker/Basket.Worker.Outbox/DependencyInjection.cs:20β src/Services/Basket/Worker/Basket.Worker.Outbox/DependencyInjection.cs:20-25 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/DependencyInjection.cs:20-25 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/DependencyInjection.cs:20-25 | src/Services/Order/Worker/Order.Woker.Outbox/DependencyInjection.cs:20-25 β the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach β a location they all depend on today, or a new shared one if there is none β and call it from each site; until then, every change has to be made 4 times. 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.
Off the main sequence: EventSourcing src/Shared/EventSourcing/EventSourcing.csproj:1β EventSourcing: abstractness 0.00, instability 0.05, distance 0.95 β zone of pain β concrete and depended on by 8 project(s), so it's rigid to change.
Low cohesion: ProductEntity (LCOM4 10) src/Services/Catalog/Core/Catalog.Domain/Entities/ProductEntity.cs:12β ProductEntity's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable β your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected β and which would otherwise dominate this list β are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Non-idempotent mutation: Commands.UpdateStockCommandHandler.Handle src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/UpdateStockCommand.cs:49β `Commands.UpdateStockCommandHandler.Handle` mutates persistent state (a database save) and accumulates `Quantity += amount` (line 109) in `InventoryItemEntity.Increase`, so a re-run applies it again. A retry or at-least-once redelivery runs it again β add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Hollow method β returns a constant without doing the work src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:52β `UseInfrastructure` looks like it should compute a result but its body just returns a constant β a placeholder return that was never filled in.
Duplication concentrated across 30 sibling directories (99 clone groups) src/Apps/App.Store/src/components/collection/CollectionSection.jsx:78β 99 duplicated blocks under src/Apps/App.Store/src/components/ have copies in at least two of the sibling directories authentication, banner, blog, brands, cart, category (+24 more sibling(s) not listed) β 49 of them are reported below, and 50 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 99 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 99 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 99 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 17 sibling directories (91 clone groups) src/Apps/App.Admin/src/pages/brand/index.jsx:274β 91 duplicated blocks under src/Apps/App.Admin/src/pages/ have copies in at least two of the sibling directories app, auth, brand, category, chart, components (+11 more sibling(s) not listed) β 63 of them are reported below, and 28 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 91 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 91 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 91 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 2 sibling directories (42 clone groups) src/Apps/App.Admin/src/api/axiosInstance.js:1β 42 duplicated blocks under src/Apps/ have copies in at least two of the sibling directories App.Admin, App.Store β 19 of them are reported below, and 23 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 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 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 6 sibling directories (34 clone groups) src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:1β 34 duplicated blocks under src/Apps/App.Admin/src/pages/app/ have copies in at least two of the sibling directories calendar, chat, email, kanban, projects, todo β 21 of them are reported below, and 13 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 34 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 34 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 34 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 (31 clone groups) src/Apps/App.Admin/src/components/partials/Table/transactions.jsx:195β 31 duplicated blocks under src/Apps/App.Admin/src/ have copies in at least two of the sibling directories components, constant, pages β 19 of them are reported below, and 12 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 31 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 31 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 31 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.
Wholesale file copy (466 identical lines × 2 files) src/Apps/App.Admin/src/pages/product/create-product.jsx:1β src/Apps/App.Admin/src/pages/product/create-product.jsx:1 · src/Apps/App.Admin/src/pages/product/edit-product.jsx:1 β these 2 files are line-for-line copies of one another β 466 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (306 identical lines × 2 files) src/Apps/App.Admin/src/pages/orders/create.jsx:1β src/Apps/App.Admin/src/pages/orders/create.jsx:1 · src/Apps/App.Admin/src/pages/orders/edit.jsx:1 β these 2 files are line-for-line copies of one another β 306 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 Β· Code DuplicationΒ· Duplicated block with local edits (256 matched lines × 2 locations) Β· Γ1
Duplicated block with local edits (256 matched lines × 2 locations) src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:66β src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:66 · src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:52 β the two spans are one implementation copied and then locally edited β 1514 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.
Wholesale file copy (209 identical lines × 2 files) src/Apps/App.Admin/src/pages/forms/form-wizard/HorizentalWizard.jsx:1β src/Apps/App.Admin/src/pages/forms/form-wizard/HorizentalWizard.jsx:1 · src/Apps/App.Admin/src/pages/forms/form-wizard/Vertical.jsx:1 β these 2 files are line-for-line copies of one another β 209 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (207 identical lines × 2 files) src/Apps/App.Store/src/components/product/GlassSection-2.jsx:1β src/Apps/App.Store/src/components/product/GlassSection-2.jsx:1 · src/Apps/App.Store/src/components/product/GlassSection.jsx:1 β these 2 files are line-for-line copies of one another β 207 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (204 identical lines × 2 files) src/Apps/App.Admin/src/api/axiosInstance.js:1β src/Apps/App.Admin/src/api/axiosInstance.js:1 · src/Apps/App.Store/src/api/axiosInstance.js:1 β these 2 files are line-for-line copies of one another β 204 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 Β· Code DuplicationΒ· Duplicated block with local edits (190 matched lines × 2 locations) Β· Γ1
Duplicated block with local edits (190 matched lines × 2 locations) src/Apps/App.Admin/src/services/keycloakService.js:29β src/Apps/App.Admin/src/services/keycloakService.js:29 · src/Apps/App.Store/src/services/keycloakService.js:41 β the two spans are one implementation copied and then locally edited β 1183 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.
Wholesale file copy (178 identical lines × 2 files) src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:1β src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:1 · src/Apps/App.Admin/src/pages/app/projects/AddProject.jsx:1 β these 2 files are line-for-line copies of one another β 178 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (171 identical lines × 2 files) src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:1β src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:1 · src/Apps/App.Admin/src/pages/app/projects/EditProject.jsx:1 β these 2 files are line-for-line copies of one another β 171 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (155 identical lines × 2 files) src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:2β src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:2 · src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:2 β these 2 files are line-for-line copies of one another β 155 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (154 identical lines × 2 files) src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:2β src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx:2 · src/Apps/App.Admin/src/pages/app/projects/AddProject.jsx:2 β these 2 files are line-for-line copies of one another β 154 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 Β· Code DuplicationΒ· Duplicated block with local edits (144 matched lines × 2 locations) Β· Γ1
Duplicated block with local edits (144 matched lines × 2 locations) src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:8β src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:8 · src/Apps/App.Store/src/contexts/KeycloakContext.jsx:5 β the two spans are one implementation copied and then locally edited β 850 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 (121 matched lines × 2 locations) Β· Γ1
Duplicated block with local edits (121 matched lines × 2 locations) src/Apps/App.Admin/src/pages/product/index.jsx:186β src/Apps/App.Admin/src/pages/product/index.jsx:186 · src/Apps/App.Admin/src/pages/product/orders.jsx:205 β the two spans are one implementation copied and then locally edited β 714 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 (118 lines × 2 locations) src/Apps/App.Admin/src/pages/brand/index.jsx:274β src/Apps/App.Admin/src/pages/brand/index.jsx:274 · src/Apps/App.Admin/src/pages/category/index.jsx:344 β 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 (116 matched lines × 2 locations) Β· Γ1
Duplicated block with local edits (116 matched lines × 2 locations) src/Apps/App.Admin/src/pages/app/email/index.jsx:29β src/Apps/App.Admin/src/pages/app/email/index.jsx:29 · src/Apps/App.Admin/src/pages/app/todo/index.jsx:75 β the two spans are one implementation copied and then locally edited β 613 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 (115 lines × 2 locations) src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:91β src/Apps/App.Admin/src/components/partials/Table/recentOrder-table.jsx:91 · src/Apps/App.Admin/src/components/partials/Table/team-table.jsx:198 β 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 (96 lines × 2 locations) src/Apps/App.Admin/src/pages/app/projects/project-details.jsx:118β src/Apps/App.Admin/src/pages/app/projects/project-details.jsx:118 · src/Apps/App.Admin/src/pages/dashboard/project.jsx:50 β 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 (93 lines × 2 locations) src/Apps/App.Admin/src/components/partials/widget/chart/account-payable.jsx:5β src/Apps/App.Admin/src/components/partials/widget/chart/account-payable.jsx:5 · src/Apps/App.Admin/src/components/partials/widget/chart/account-receivable.jsx:5 β 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 (90 lines × 2 locations) src/Apps/App.Admin/src/pages/inventory/index.jsx:1411β src/Apps/App.Admin/src/pages/inventory/index.jsx:1411 · src/Apps/App.Admin/src/pages/inventory/index.jsx:1607 β 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 (88 lines × 4 locations) src/Apps/App.Admin/src/pages/coupon/index.jsx:675β src/Apps/App.Admin/src/pages/coupon/index.jsx:675 · src/Apps/App.Admin/src/pages/orders/index.jsx:685 · src/Apps/App.Admin/src/pages/product/index.jsx:526 · src/Apps/App.Admin/src/pages/product/orders.jsx:478 β the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block β it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead β the whole function, component or branch these lines sit in β and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (86 lines × 3 locations) src/Apps/App.Admin/src/pages/app/projects/ProjectList.jsx:247β src/Apps/App.Admin/src/pages/app/projects/ProjectList.jsx:247 · src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:310 · src/Apps/App.Admin/src/pages/utility/invoice.jsx:343 β the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block β it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead β the whole function, component or branch these lines sit in β and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 Β· Code DuplicationΒ· Duplicated block with local edits (86 matched lines × 2 locations) Β· Γ1
Duplicated block with local edits (86 matched lines × 2 locations) src/Apps/App.Store/src/context/FarzaaContext.jsx:821β src/Apps/App.Store/src/context/FarzaaContext.jsx:821 · src/Apps/App.Store/src/context/FarzaaContext.jsx:972 β the two spans are one implementation copied and then locally edited β 437 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters β or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 Β· Code DuplicationΒ· Duplicated block with local edits (83 matched lines × 2 locations) Β· Γ1
Duplicated block with local edits (83 matched lines × 2 locations) src/Apps/App.Admin/src/components/ui/InputGroup.jsx:34β src/Apps/App.Admin/src/components/ui/InputGroup.jsx:34 · src/Apps/App.Admin/src/components/ui/Textinput.jsx:32 β the two spans are one implementation copied and then locally edited β 363 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 (82 lines × 4 locations) src/Apps/App.Admin/src/pages/notification/index.jsx:399β src/Apps/App.Admin/src/pages/notification/index.jsx:399 · src/Apps/App.Admin/src/pages/orders/index.jsx:685 · src/Apps/App.Admin/src/pages/product/index.jsx:526 · src/Apps/App.Admin/src/pages/product/orders.jsx:478 β the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block β it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead β the whole function, component or branch these lines sit in β and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (82 lines × 2 locations) src/Apps/App.Admin/src/pages/orders/details.jsx:532β src/Apps/App.Admin/src/pages/orders/details.jsx:532 · src/Apps/App.Admin/src/pages/orders/index.jsx:778 β 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 (81 lines × 2 locations) src/Apps/App.Store/src/components/header/HeaderSection7.jsx:33β src/Apps/App.Store/src/components/header/HeaderSection7.jsx:33 · src/Apps/App.Store/src/components/header/HeaderSection8.jsx:84 β the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (80 lines × 2 locations) src/Apps/App.Admin/src/pages/product/orders.jsx:413β src/Apps/App.Admin/src/pages/product/orders.jsx:413 · src/Apps/App.Admin/src/pages/table/react-tables/ExampleTwo.jsx:219 β 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 (75 lines × 2 locations) src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:159β src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsx:159 · src/Apps/App.Admin/src/pages/table/react-tables/ExampleTwo.jsx:133 β 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.
Wholesale file copy (74 identical lines × 3 files) src/Apps/App.Store/src/components/sliders/CupCakeSlider.jsx:1β src/Apps/App.Store/src/components/sliders/CupCakeSlider.jsx:1 · src/Apps/App.Store/src/components/sliders/LayerCakeSlider.jsx:1 · src/Apps/App.Store/src/components/sliders/PoundCakeSlider.jsx:1 β these 3 files are line-for-line copies of one another β 74 lines are identical, in the same order, in every one of them β so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) β the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Complex function OrderDetails (cyclomatic 63, cognitive 52) src/Apps/App.Admin/src/pages/orders/details.jsx:63β OrderDetails has cyclomatic complexity 63 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function InventoryPage (cyclomatic 48, cognitive 47) src/Apps/App.Admin/src/pages/inventory/index.jsx:53β InventoryPage has cyclomatic complexity 48 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 47, cognitive 35) src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:163β (anonymous) has cyclomatic complexity 47 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ProductDetails (cyclomatic 44, cognitive 39) src/Apps/App.Admin/src/pages/product/productDetails.jsx:35β ProductDetails has cyclomatic complexity 44 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function InputGroup (cyclomatic 41, cognitive 34) src/Apps/App.Admin/src/components/ui/InputGroup.jsx:6β InputGroup has cyclomatic complexity 41 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function CouponPage (cyclomatic 40, cognitive 36) src/Apps/App.Admin/src/pages/coupon/index.jsx:36β CouponPage has cyclomatic complexity 40 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Button (cyclomatic 40, cognitive 30) src/Apps/App.Admin/src/components/ui/Button.jsx:4β Button has cyclomatic complexity 40 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Modal (cyclomatic 35, cognitive 34) src/Apps/App.Admin/src/components/ui/Modal.jsx:5β Modal has cyclomatic complexity 35 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Textinput (cyclomatic 29, cognitive 26) src/Apps/App.Admin/src/components/ui/Textinput.jsx:5β Textinput has cyclomatic complexity 29 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function CreateCoupon (cyclomatic 25, cognitive 24) src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:15β CreateCoupon has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetchOrder (cyclomatic 25, cognitive 22) src/Apps/App.Admin/src/pages/orders/edit.jsx:53β fetchOrder has cyclomatic complexity 25 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getInitialValues (cyclomatic 24, cognitive 22) src/Apps/App.Admin/src/pages/product/edit-product.jsx:144β getInitialValues has cyclomatic complexity 24 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Ecommerce (cyclomatic 23, cognitive 22) src/Apps/App.Admin/src/pages/product/index.jsx:43β Ecommerce has cyclomatic complexity 23 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function OrderDetailModal (cyclomatic 23, cognitive 20) src/Apps/App.Store/src/components/modal/OrderDetailModal.jsx:17β OrderDetailModal has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetchProducts (cyclomatic 23, cognitive 19) src/Apps/App.Store/src/context/FarzaaContext.jsx:244β fetchProducts has cyclomatic complexity 23 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onSubmit (cyclomatic 21, cognitive 18) src/Apps/App.Admin/src/pages/product/create-product.jsx:136β onSubmit has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth β arms side by side rather than stacked β and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/inventory/index.jsx Β· Γ1
src/Apps/App.Admin/src/pages/inventory/index.jsx: 1724 lines of code src/Apps/App.Admin/src/pages/inventory/index.jsx:1β src/Apps/App.Admin/src/pages/inventory/index.jsx has 1724 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Store/src/context/FarzaaContext.jsx Β· Γ1
src/Apps/App.Store/src/context/FarzaaContext.jsx: 1102 lines of code src/Apps/App.Store/src/context/FarzaaContext.jsx:1β src/Apps/App.Store/src/context/FarzaaContext.jsx has 1102 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/coupon/index.jsx Β· Γ1
src/Apps/App.Admin/src/pages/coupon/index.jsx: 1034 lines of code src/Apps/App.Admin/src/pages/coupon/index.jsx:1β src/Apps/App.Admin/src/pages/coupon/index.jsx has 1034 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/orders/index.jsx Β· Γ1
src/Apps/App.Admin/src/pages/orders/index.jsx: 865 lines of code src/Apps/App.Admin/src/pages/orders/index.jsx:1β src/Apps/App.Admin/src/pages/orders/index.jsx has 865 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/category/index.jsx Β· Γ1
src/Apps/App.Admin/src/pages/category/index.jsx: 768 lines of code src/Apps/App.Admin/src/pages/category/index.jsx:1β src/Apps/App.Admin/src/pages/category/index.jsx has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/constant/data.js Β· Γ1
src/Apps/App.Admin/src/constant/data.js: 717 lines of code src/Apps/App.Admin/src/constant/data.js:1β src/Apps/App.Admin/src/constant/data.js has 717 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/product/index.jsx Β· Γ1
src/Apps/App.Admin/src/pages/product/index.jsx: 707 lines of code src/Apps/App.Admin/src/pages/product/index.jsx:1β src/Apps/App.Admin/src/pages/product/index.jsx has 707 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/product/edit-product.jsx Β· Γ1
src/Apps/App.Admin/src/pages/product/edit-product.jsx: 701 lines of code src/Apps/App.Admin/src/pages/product/edit-product.jsx:1β src/Apps/App.Admin/src/pages/product/edit-product.jsx has 701 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/product/productDetails.jsx Β· Γ1
src/Apps/App.Admin/src/pages/product/productDetails.jsx: 677 lines of code src/Apps/App.Admin/src/pages/product/productDetails.jsx:1β src/Apps/App.Admin/src/pages/product/productDetails.jsx has 677 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/product/create-product.jsx Β· Γ1
src/Apps/App.Admin/src/pages/product/create-product.jsx: 643 lines of code src/Apps/App.Admin/src/pages/product/create-product.jsx:1β src/Apps/App.Admin/src/pages/product/create-product.jsx has 643 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/brand/index.jsx Β· Γ1
src/Apps/App.Admin/src/pages/brand/index.jsx: 641 lines of code src/Apps/App.Admin/src/pages/brand/index.jsx:1β src/Apps/App.Admin/src/pages/brand/index.jsx has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/orders/details.jsx Β· Γ1
src/Apps/App.Admin/src/pages/orders/details.jsx: 629 lines of code src/Apps/App.Admin/src/pages/orders/details.jsx:1β src/Apps/App.Admin/src/pages/orders/details.jsx has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/components/modal.jsx Β· Γ1
src/Apps/App.Admin/src/pages/components/modal.jsx: 604 lines of code src/Apps/App.Admin/src/pages/components/modal.jsx:1β src/Apps/App.Admin/src/pages/components/modal.jsx has 604 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/product/orders.jsx Β· Γ1
src/Apps/App.Admin/src/pages/product/orders.jsx: 589 lines of code src/Apps/App.Admin/src/pages/product/orders.jsx:1β src/Apps/App.Admin/src/pages/product/orders.jsx has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/constant/appex-chart.js Β· Γ1
src/Apps/App.Admin/src/constant/appex-chart.js: 568 lines of code src/Apps/App.Admin/src/constant/appex-chart.js:1β src/Apps/App.Admin/src/constant/appex-chart.js has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/components/card.jsx Β· Γ1
src/Apps/App.Admin/src/pages/components/card.jsx: 550 lines of code src/Apps/App.Admin/src/pages/components/card.jsx:1β src/Apps/App.Admin/src/pages/components/card.jsx has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/components/dropdown.jsx Β· Γ1
src/Apps/App.Admin/src/pages/components/dropdown.jsx: 542 lines of code src/Apps/App.Admin/src/pages/components/dropdown.jsx:1β src/Apps/App.Admin/src/pages/components/dropdown.jsx has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/components/typography.jsx Β· Γ1
src/Apps/App.Admin/src/pages/components/typography.jsx: 483 lines of code src/Apps/App.Admin/src/pages/components/typography.jsx:1β src/Apps/App.Admin/src/pages/components/typography.jsx has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/components/colors.jsx Β· Γ1
src/Apps/App.Admin/src/pages/components/colors.jsx: 478 lines of code src/Apps/App.Admin/src/pages/components/colors.jsx:1β src/Apps/App.Admin/src/pages/components/colors.jsx has 478 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/orders/edit.jsx Β· Γ1
src/Apps/App.Admin/src/pages/orders/edit.jsx: 473 lines of code src/Apps/App.Admin/src/pages/orders/edit.jsx:1β src/Apps/App.Admin/src/pages/orders/edit.jsx has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/product/add-product.jsx Β· Γ1
src/Apps/App.Admin/src/pages/product/add-product.jsx: 473 lines of code src/Apps/App.Admin/src/pages/product/add-product.jsx:1β src/Apps/App.Admin/src/pages/product/add-product.jsx has 473 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx Β· Γ1
src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx: 472 lines of code src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:1β src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/notification/index.jsx Β· Γ1
src/Apps/App.Admin/src/pages/notification/index.jsx: 453 lines of code src/Apps/App.Admin/src/pages/notification/index.jsx:1β src/Apps/App.Admin/src/pages/notification/index.jsx has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/orders/create.jsx Β· Γ1
src/Apps/App.Admin/src/pages/orders/create.jsx: 430 lines of code src/Apps/App.Admin/src/pages/orders/create.jsx:1β src/Apps/App.Admin/src/pages/orders/create.jsx has 430 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Store/src/services/keycloakService.js Β· Γ1
src/Apps/App.Store/src/services/keycloakService.js: 427 lines of code src/Apps/App.Store/src/services/keycloakService.js:1β src/Apps/App.Store/src/services/keycloakService.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/product/orderDetails.jsx Β· Γ1
src/Apps/App.Admin/src/pages/product/orderDetails.jsx: 424 lines of code src/Apps/App.Admin/src/pages/product/orderDetails.jsx:1β src/Apps/App.Admin/src/pages/product/orderDetails.jsx has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx Β· Γ1
src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx: 423 lines of code src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:1β src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
R3 Β· Large FilesΒ· src/Apps/App.Admin/src/pages/utility/invoice.jsx Β· Γ1
src/Apps/App.Admin/src/pages/utility/invoice.jsx: 418 lines of code src/Apps/App.Admin/src/pages/utility/invoice.jsx:1β src/Apps/App.Admin/src/pages/utility/invoice.jsx has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic β a file this long is usually several responsibilities in one module.
Test Coverage β 0% of 644 production file(s) reachable from 0 test file(s) via the import graph β 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
Dead file (~606 LoC) src/Apps/App.Admin/src/pages/components/modal.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~592 LoC) src/Apps/App.Admin/src/constant/appex-chart.jsβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~557 LoC) src/Apps/App.Admin/src/pages/components/card.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~545 LoC) src/Apps/App.Admin/src/pages/components/dropdown.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~498 LoC) src/Apps/App.Admin/src/pages/components/typography.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~492 LoC) src/Apps/App.Admin/src/pages/components/colors.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~482 LoC) src/Apps/App.Admin/src/pages/product/add-product.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~446 LoC) src/Apps/App.Admin/src/pages/product/orderDetails.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~399 LoC) src/Apps/App.Admin/src/pages/table/react-tables/ExampleOne.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/table/react-table.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~381 LoC) src/Apps/App.Admin/src/pages/table/react-tables/ExampleTwo.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Apps/App.Admin/src/pages/dashboard/crm.jsx, src/Apps/App.Admin/src/pages/table/react-table.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~374 LoC) src/Apps/App.Admin/src/pages/components/alert.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~334 LoC) src/Apps/App.Admin/src/pages/app/projects/ProjectList.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/projects/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~329 LoC) src/Apps/App.Admin/src/pages/widget/basic-widget.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~322 LoC) src/Apps/App.Admin/src/components/partials/Table/team-table.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Apps/App.Admin/src/pages/app/projects/project-details.jsx, src/Apps/App.Admin/src/pages/dashboard/project.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~314 LoC) src/Apps/App.Admin/src/pages/chart/appex-chart/Candlestick.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/chart/appex-chart/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~303 LoC) src/Apps/App.Admin/src/pages/product/Ecommerce.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~288 LoC) src/Apps/App.Admin/src/pages/components/tab-accordion.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~287 LoC) src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/kanban/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~285 LoC) src/Apps/App.Admin/src/pages/app/projects/EditProject.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/projects/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~284 LoC) src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/kanban/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~274 LoC) src/Apps/App.Admin/src/pages/app/projects/AddProject.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/projects/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~273 LoC) src/Apps/App.Admin/src/components/partials/Table/transactions.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/dashboard/banking.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~271 LoC) src/Apps/App.Admin/src/components/partials/widget/chart/group-chart5.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Apps/App.Admin/src/pages/dashboard/banking.jsx, src/Apps/App.Admin/src/pages/widget/statistic-widget.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~265 LoC) src/Apps/App.Admin/src/pages/utility/pricing.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~245 LoC) src/Apps/App.Admin/src/pages/app/calendar/index.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~244 LoC) src/Apps/App.Admin/src/pages/forms/input-group.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~239 LoC) src/Apps/App.Admin/src/pages/app/todo/EditTodo.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/todo/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~236 LoC) src/Apps/App.Admin/src/pages/app/chat/Chat.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/chat/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~233 LoC) src/Apps/App.Admin/src/pages/utility/blog/index.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~224 LoC) src/Apps/App.Admin/src/pages/app/todo/index.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~215 LoC) src/Apps/App.Admin/src/pages/app/projects/project-details.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it β nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~207 LoC) src/Apps/App.Admin/src/pages/app/calendar/EventModal.jsxβ no import path from any entry point (15 application, 4 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Apps/App.Admin/src/pages/app/calendar/index.jsx) β every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~199 LoC) src/Apps/App.Admin/src/pages/components/badges.jsxβ no import path from any entry point (15 application, 4 tooling, 0 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 '@dnd-kit/modifiers' β Declared in src/Apps/App.Admin/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 '@dnd-kit/sortable' β Declared in src/Apps/App.Admin/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 '@dnd-kit/utilities' β Declared in src/Apps/App.Admin/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.
Token validation disabled src/Shared/BuildingBlocks/Authentication/Extensions/AuthorizationExtension.cs:45β `ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent.
X24 Β· Document value interpolated into markup unescapedΒ· Untrusted text written into markup unescaped Β· Γ1
Untrusted text written into markup unescaped src/Apps/App.Admin/src/components/ui/Accordion.jsx:48β `item.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
redundant comment src/ApiGateway/YarpApiGateway/Program.cs:13β "Add services to the container." is ASP.NET Core project template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/ApiGateway/YarpApiGateway/Program.cs:43β "Configure the HTTP request pipeline." is ASP.NET Core project template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/api/axiosInstance.js:37β 6 comments in this file only repeat the code they sit on (lines 37, 96, 105, 117, 134, 209), for example "Check if translation exists for the error key". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/components/partials/header/Tools/Notification.jsx:83β "Format time ago" repeats the code it sits on: 3 of its 3 words (format, time, ago) are already in `const formatTimeAgo = (dateString) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/components/partials/header/Tools/Notification.jsx:109β "Handle notification click" repeats the code it sits on: 3 of its 3 words (handle, notification, click) are already in `const handleNotificationClick = async (notification) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/components/skeleton/Grid.jsx:4β "set items length by count" repeats the code it sits on: 4 of its 4 words (set, items, length, count) are already in `items = items || Array.from({ length: count });`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:157β "Set up token refresh interval" repeats the code it sits on: 4 of its 4 words (set, token, refresh, interval) are already in `tokenRefreshIntervalRef.current = setInterval(() =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/app/calendar/index.jsx:95β "handle close modal" repeats the code it sits on: 3 of its 3 words (handle, close, modal) are already in `const handleCloseModal = () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/auth/common/reg-from.jsx:52β "Log the error response to the console for debugging" repeats the code it sits on: 4 of its 5 words (log, error, response, console) are already in `console.log(error.response);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/coupon/create-coupon.jsx:25β "Yup validation schema" repeats the code it sits on: 3 of its 3 words (yup, validation, schema) are already in `const validationSchema = Yup.object({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/coupon/edit-coupon.jsx:24β "Yup validation schema" repeats the code it sits on: 3 of its 3 words (yup, validation, schema) are already in `const validationSchema = Yup.object({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/inventory/index.jsx:80β 7 comments in this file only repeat the code they sit on (lines 80, 87, 94, 295, 362, 426, 496), for example "Form data for add". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/notification/index.jsx:90β "Format time ago" repeats the code it sits on: 3 of its 3 words (format, time, ago) are already in `const formatTimeAgo = (dateString) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/notification/index.jsx:116β "Handle notification click" repeats the code it sits on: 3 of its 3 words (handle, notification, click) are already in `const handleNotificationClick = async (notification) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/notification/index.jsx:139β "Handle mark selected as read" repeats the code it sits on: 4 of its 4 words (handle, mark, selected, read) are already in `const handleMarkSelectedAsRead = async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/product/create-product.jsx:73β "Yup validation schema" repeats the code it sits on: 3 of its 3 words (yup, validation, schema) are already in `const validationSchema = Yup.object({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/product/edit-product.jsx:104β "Yup validation schema" repeats the code it sits on: 3 of its 3 words (yup, validation, schema) are already in `const validationSchema = Yup.object({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/pages/product/productDetails.jsx:65β "Get status config for displayStatus badge" repeats the code it sits on: 4 of its 5 words (get, status, config, display) are already in `const getStatusConfig = (displayStatus) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/services/keycloakService.js:120β "Delete access token cookie on logout" repeats the code it sits on: 4 of its 5 words (delete, access, token, cookie) are already in `deleteAccessTokenCookie();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Admin/src/services/keycloakService.js:226β "Delete access token cookie before logout" repeats the code it sits on: 4 of its 5 words (delete, access, token, cookie) are already in `deleteAccessTokenCookie();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Store/src/api/axiosInstance.js:37β 6 comments in this file only repeat the code they sit on (lines 37, 95, 104, 116, 133, 210), for example "Check if translation exists for the error key". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:27β "Success modal state" repeats the code it sits on: 3 of its 3 words (success, modal, state) are already in `const [showSuccessModal, setShowSuccessModal] = useState(false);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:36β "Validation schema with Yup" repeats the code it sits on: 3 of its 3 words (validation, schema, yup) are already in `const validationSchema = Yup.object({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:82β "Handle apply coupon" repeats the code it sits on: 3 of its 3 words (handle, apply, coupon) are already in `const handleApplyCoupon = async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Apps/App.Store/src/components/checkout/CheckoutSection.jsx:109β "Handle remove coupon" repeats the code it sits on: 3 of its 3 words (handle, remove, coupon) are already in `const handleRemoveCoupon = () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
+ 57 more in this group β see findings.md.
DM2 Β· Strongly-typed idsΒ· Primitive id on a domain type Β· Γ40
Primitive id on a domain type: IDomainEvent.EventId src/Services/Catalog/Core/Catalog.Domain/Abstractions/IDomainEvent.cs:13β `IDomainEvent.EventId` 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: CategoryEntity.ParentId src/Services/Catalog/Core/Catalog.Domain/Entities/CategoryEntity.cs:19β `CategoryEntity.ParentId` 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: ProductEntity.BrandId src/Services/Catalog/Core/Catalog.Domain/Entities/ProductEntity.cs:50β `ProductEntity.BrandId` 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: DeletedUnPublishedProductDomainEvent.ProductId src/Services/Catalog/Core/Catalog.Domain/Events/DeletedUnPublishedProductDomainEvent.cs:9β `DeletedUnPublishedProductDomainEvent.ProductId` 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: IDomainEvent.EventId src/Services/Inventory/Core/Inventory.Domain/Abstractions/IDomainEvent.cs:13β `IDomainEvent.EventId` 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: InventoryItemEntity.LocationId src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs:26β `InventoryItemEntity.LocationId` 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: InventoryReservationEntity.ReferenceId src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs:18β `InventoryReservationEntity.ReferenceId` 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: InventoryReservationEntity.LocationId src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs:26β `InventoryReservationEntity.LocationId` 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: LocationChangedDomainEvent.InventoryItemId src/Services/Inventory/Core/Inventory.Domain/Events/LocationChangedDomainEvent.cs:10β `LocationChangedDomainEvent.InventoryItemId` 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: LocationChangedDomainEvent.ProductId src/Services/Inventory/Core/Inventory.Domain/Events/LocationChangedDomainEvent.cs:11β `LocationChangedDomainEvent.ProductId` 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: ReservationCommittedDomainEvent.ReservationId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:10β `ReservationCommittedDomainEvent.ReservationId` 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: ReservationCommittedDomainEvent.ProductId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:11β `ReservationCommittedDomainEvent.ProductId` 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: ReservationCommittedDomainEvent.ReferenceId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:13β `ReservationCommittedDomainEvent.ReferenceId` 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: ReservationCommittedDomainEvent.LocationId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCommittedDomainEvent.cs:14β `ReservationCommittedDomainEvent.LocationId` 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: ReservationCreatedDomainEvent.ReservationId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:10β `ReservationCreatedDomainEvent.ReservationId` 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: ReservationCreatedDomainEvent.ProductId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:11β `ReservationCreatedDomainEvent.ProductId` 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: ReservationCreatedDomainEvent.ReferenceId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:13β `ReservationCreatedDomainEvent.ReferenceId` 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: ReservationCreatedDomainEvent.LocationId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationCreatedDomainEvent.cs:14β `ReservationCreatedDomainEvent.LocationId` 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: ReservationExpiredDomainEvent.ReservationId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:10β `ReservationExpiredDomainEvent.ReservationId` 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: ReservationExpiredDomainEvent.ProductId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:11β `ReservationExpiredDomainEvent.ProductId` 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: ReservationExpiredDomainEvent.ReferenceId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:13β `ReservationExpiredDomainEvent.ReferenceId` 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: ReservationExpiredDomainEvent.LocationId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationExpiredDomainEvent.cs:14β `ReservationExpiredDomainEvent.LocationId` 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: ReservationReleasedDomainEvent.ReservationId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationReleasedDomainEvent.cs:10β `ReservationReleasedDomainEvent.ReservationId` 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: ReservationReleasedDomainEvent.ProductId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationReleasedDomainEvent.cs:11β `ReservationReleasedDomainEvent.ProductId` 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: ReservationReleasedDomainEvent.ReferenceId src/Services/Inventory/Core/Inventory.Domain/Events/ReservationReleasedDomainEvent.cs:13β `ReservationReleasedDomainEvent.ReferenceId` is a raw `Guid` β give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Commented-out code src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:47β 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 src/Services/Catalog/Core/Catalog.Infrastructure/Repositories/OutboxRepository.cs:50β A line of code has been commented out rather than removed β dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Services/Catalog/Core/Catalog.Infrastructure/Repositories/OutboxRepository.cs:96β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:26β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:32β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:36β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:40β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:41β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:57β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:65β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:68β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:69β A line of code has been commented out rather than removed β dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:73β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:74β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:76β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:77β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:81β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:82β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:87β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:88β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs: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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:109β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:112β 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 src/Services/Discount/Core/Discount.Application/Repositories/UnitOfWorkUsageExample.cs:113β A line of code has been commented out rather than removed β dead weight that rots and confuses. Delete it (version control remembers).
Duplicated predicate src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs:48β `(req.ImageFiles == null || req.ImageFiles.Count == 0) && httpContext.HttpContext != null` appears character-identically in 2 files β src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs, src/Services/Catalog/Api/Catalog.Api/Endpoints/UpdateProduct.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 src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:102β `AttemptCount < MaxAttempts && (NextAttemptOnUtc == null || currentTime >= NextAttemptOnUtc.Value)` appears character-identically in 5 files β src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs, src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs, src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs, src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.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 src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.cs:25β `entry.References.Any(r => r.TargetEntry != null && r.TargetEntry.Metadata.IsOwned() && (r.TargetEntry.State == EntityState.Added || r.Targetβ¦` appears character-identically in 2 files β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.cs, src/Services/Order/Core/Order.Infrastructure/Data/Extensions/AuditableEntityInterceptorExtensions.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 src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs:46β `entry.State == EntityState.Modified || entry.HasChangedOwnedEntities()` appears character-identically in 2 files β src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs, src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.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 src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:55β `!keycloak || typeof keycloak !== 'object'` appears character-identically in 2 files β src/Apps/App.Admin/src/contexts/KeycloakContext.jsx, src/Apps/App.Store/src/contexts/KeycloakContext.jsx. 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 src/Apps/App.Admin/src/utils/format.js:27β `!originalPrice || !salePrice || originalPrice <= 0 || salePrice <= 0` appears character-identically in 2 files β src/Apps/App.Admin/src/utils/format.js, src/Apps/App.Store/src/utils/format.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 src/Apps/App.Admin/src/pages/orders/details.jsx:100β `ORDER_STATUS_MAP[order.status] || "pending"` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/details.jsx, src/Apps/App.Admin/src/pages/orders/index.jsx. 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 src/Apps/App.Store/src/components/header/HeaderSection5.jsx:32β `actionsRef.current && !actionsRef.current.contains(event.target)` appears character-identically in 2 files β src/Apps/App.Store/src/components/header/HeaderSection5.jsx, src/Apps/App.Store/src/components/header/HeaderSection6.jsx. 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 src/Apps/App.Admin/src/api/axiosInstance.js:54β `data?.errors && Array.isArray(data.errors) && data.errors.length > 0` appears character-identically in 2 files β src/Apps/App.Admin/src/api/axiosInstance.js, src/Apps/App.Store/src/api/axiosInstance.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 src/Apps/App.Admin/src/services/keycloakService.js:311β `decoded.given_name && decoded.family_name` appears character-identically in 2 files β src/Apps/App.Admin/src/services/keycloakService.js, src/Apps/App.Store/src/services/keycloakService.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 src/Apps/App.Admin/src/services/keycloakService.js:307β `decoded.preferred_username || decoded.username || 'user'` appears character-identically in 2 files β src/Apps/App.Admin/src/services/keycloakService.js, src/Apps/App.Store/src/services/keycloakService.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 src/Apps/App.Admin/src/services/keycloakService.js:306β `decoded.sub || keycloak.subject || 'unknown'` appears character-identically in 2 files β src/Apps/App.Admin/src/services/keycloakService.js, src/Apps/App.Store/src/services/keycloakService.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 src/Apps/App.Admin/src/pages/product/index.jsx:24β `displayStatus === "Hidden" || displayStatus === "hidden"` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/product/index.jsx, src/Apps/App.Admin/src/pages/product/productDetails.jsx. 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 src/Apps/App.Admin/src/pages/orders/details.jsx:556β `e.target.value !== "6" && e.target.value !== "7"` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/details.jsx, src/Apps/App.Admin/src/pages/orders/index.jsx. 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 src/Apps/App.Admin/src/pages/app/email/ComposeEmail.jsx:143β `errors.assign?.message || errors.assign?.label.message` appears character-identically in 7 files β src/Apps/App.Admin/src/pages/app/email/ComposeEmail.jsx, src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx, src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx, src/Apps/App.Admin/src/pages/app/projects/AddProject.jsx. 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 src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx:269β `errors.tags?.message || errors.tags?.label.message` appears character-identically in 6 files β src/Apps/App.Admin/src/pages/app/kanban/AddTaskModal.jsx, src/Apps/App.Admin/src/pages/app/kanban/EditTask.jsx, src/Apps/App.Admin/src/pages/app/projects/AddProject.jsx, src/Apps/App.Admin/src/pages/app/projects/EditProject.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:211β `formik.touched.customerEmail && formik.errors.customerEmail` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:196β `formik.touched.customerName && formik.errors.customerName` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:226β `formik.touched.customerPhoneNumber && formik.errors.customerPhoneNumber` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:249β `formik.touched.shippingAddressLine && formik.errors.shippingAddressLine` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:279β `formik.touched.shippingCity && formik.errors.shippingCity` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:309β `formik.touched.shippingCountry && formik.errors.shippingCountry` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:323β `formik.touched.shippingPostalCode && formik.errors.shippingPostalCode` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:293β `formik.touched.shippingStateOrProvince && formik.errors.shippingStateOrProvince` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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 src/Apps/App.Admin/src/pages/orders/create.jsx:265β `formik.touched.shippingSubdivision && formik.errors.shippingSubdivision` appears character-identically in 2 files β src/Apps/App.Admin/src/pages/orders/create.jsx, src/Apps/App.Admin/src/pages/orders/edit.jsx. 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.
Orphaned file src/JobOrchestrator/App.Job/Jobs/Report/SyncDashboardReportJob.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 src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCreatedIntegrationEventHandler.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 src/JobOrchestrator/App.Job/DependencyInjection.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 src/JobOrchestrator/App.Job/Quartz/JobRegistrationExtensions.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 src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/UpdateInventoryItemCommand.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 src/Services/Communication/Api/Communication.Api/Services/NotificationHubService.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 src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderStatusCommand.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 src/Services/Catalog/Core/Catalog.Infrastructure/Data/BrandSeedData.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 src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/Repository.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 src/Services/Order/Core/Order.Infrastructure/Repositories/Repository.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 src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ReserveInventoryCommand.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 src/Services/Order/Worker/Order.Worker.Consumer/EventHandlers/Integrations/ReservationExpiredIntegrationEventHandler.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 src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderDeliveredIntegrationEventHandler.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 src/Services/Order/Api/Order.Grpc/Services/OrderGrpcService.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 src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.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 src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.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 src/Services/Catalog/Core/Catalog.Infrastructure/Data/CategorySeedData.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 src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ExpireReservationCommand.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 src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCancelledIntegrationEventHandler.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 src/Services/Report/Api/Report.Grpc/Services/ReportGrpcService.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 src/Services/Catalog/Core/Catalog.Application/Features/Category/Commands/UpdateCategoryCommand.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 src/Services/Order/Core/Order.Infrastructure/Repositories/OrderRepository.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.
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 src/ApiGateway/YarpApiGateway/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 src/Services/Basket/Api/Basket.Api/Program.cs:9β 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 src/Services/Catalog/Api/Catalog.Api/Program.cs:9β 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 src/Services/Catalog/Api/Catalog.Grpc/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 REDACTED: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 src/Services/Discount/Api/Discount.Api/Program.cs:9β 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 src/Services/Discount/Api/Discount.Grpc/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 src/Services/Inventory/Api/Inventory.Api/Program.cs:9β 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 src/Services/Inventory/Api/Inventory.Grpc/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 src/Services/Notification/Api/Notification.Api/Program.cs:9β 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 src/Services/Order/Api/Order.Api/Program.cs:9β 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 src/Services/Order/Api/Order.Grpc/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 src/Services/Report/Api/Report.Api/Program.cs:9β 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 src/Services/Report/Api/Report.Grpc/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 src/Services/Search/Api/Search.Api/Program.cs:9β 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 app-layer HTTPS enforcement detected β No UseHttpsRedirection/UseHsts and no reverse-proxy signal β transport security is unverified at the app layer. (β2.0 on this card.)
No app-layer HTTPS enforcement detected src/ApiGateway/YarpApiGateway/Program.cs:11β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Basket/Api/Basket.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Catalog/Api/Catalog.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Catalog/Api/Catalog.Grpc/Program.cs:12β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected REDACTED:7β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Discount/Api/Discount.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Discount/Api/Discount.Grpc/Program.cs:12β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Inventory/Api/Inventory.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Inventory/Api/Inventory.Grpc/Program.cs:12β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Notification/Api/Notification.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Order/Api/Order.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Order/Api/Order.Grpc/Program.cs:12β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Report/Api/Report.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Report/Api/Report.Grpc/Program.cs:11β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Services/Search/Api/Search.Api/Program.cs:9β This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
X7 Β· Silent fallback defaultsΒ· Pending state with no failure state Β· Γ11
Pending state with no failure state src/Apps/App.Store/src/contexts/KeycloakContext.jsx:278β The view draws `Loading...` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Store/src/components/shop/ProductContainer.jsx:21β The view draws `Loading...` under `productsLoading`, but `productsLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Store/src/components/modal/OrderDetailModal.jsx:83β The view draws `<div class="text-center py-5">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Store/src/components/main/MyOrdersMain.jsx:59β The view draws `<div class="text-center py-5">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Store/src/components/auth/ProtectedRoute.jsx:41β The view draws `Loading...` under `! keycloakReady || isProcessingCallback ( )`, but `keycloakReady` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Admin/src/pages/utility/profile.jsx:36β The view draws `<div class="flex items-center justify-center min-h-[400px]">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Admin/src/pages/forms/file-input/DropZone.jsx:31β The view draws `Drop the files here ...` under `isDragAccept`, but `isDragAccept` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Admin/src/contexts/KeycloakContext.jsx:208β The view draws `<Loading/>` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Admin/src/components/Loading.jsx:39β The view draws `Loading ...` under `isAuth`, but `isAuth` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Admin/src/components/auth/RootRedirect.jsx:26β The view draws `<Loading/>` under `! keycloakReady`, but `keycloakReady` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Pending state with no failure state src/Apps/App.Admin/src/components/auth/RootRedirect.jsx:31β The view draws `<Loading/>` under `! authenticated`, but `authenticated` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Shell project: Catalog.Contract src/Shared/Contracts/Catalog.Contract/Catalog.Contract.csprojβ `Catalog.Contract` contributes only 0 significant line(s) β an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Discount.Contract src/Shared/Contracts/Discount.Contract/Discount.Contract.csprojβ `Discount.Contract` contributes only 0 significant line(s) β an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Order.Contract src/Shared/Contracts/Order.Contract/Order.Contract.csprojβ `Order.Contract` contributes only 0 significant line(s) β an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Report.Contract src/Shared/Contracts/Report.Contract/Report.Contract.csprojβ `Report.Contract` contributes only 0 significant line(s) β an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Shell project: Inventory.Contract src/Shared/Contracts/Inventory.Contract/Inventory.Contract.csprojβ `Inventory.Contract` contributes only 0 significant line(s) β an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
ED3 Β· Event namingΒ· Event not named in past tense Β· Γ3
Event not named in past tense: BasketCheckoutIntegrationEvent src/Shared/EventSourcing/Events/Baskets/BasketCheckoutIntegrationEvent.cs:3β `BasketCheckoutIntegrationEvent` 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: TransferOutDomainEvent src/Services/Inventory/Core/Inventory.Domain/Events/TransferOutDomainEvent.cs:9β `TransferOutDomainEvent` 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: BasketCheckoutDomainEvent src/Services/Basket/Core/Basket.Domain/Events/BasketCheckoutDomainEvent.cs:10β `BasketCheckoutDomainEvent` 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.
X7 Β· Silent fallback defaultsΒ· Silent fallback default on configuration miss Β· Γ3
Silent fallback default on configuration miss src/Shared/BuildingBlocks/DistributedTracing/DistributedTracingExtension.cs:27β `AddDistributedTracing` reads `cfg.GetValue($"{DistributedTracingCfg.Section}:{DistributedTracingCfg.Enable}", β¦` β a missing or misspelt key silently becomes `false`, with no log or throw. Validate the options at startup (or log the miss); if that constant is the specified default, document it on the member and the row stops firing.
Silent fallback default on configuration miss src/Shared/BuildingBlocks/DistributedTracing/DistributedTracingExtension.cs:113β `UsePrometheusEndpoint` reads `cfg.GetValue($"{DistributedTracingCfg.Section}:{DistributedTracingCfg.Enable}", β¦` β a missing or misspelt key silently becomes `false`, with no log or throw. Validate the options at startup (or log the miss); if that constant is the specified default, document it on the member and the row stops firing.
Silent fallback default on configuration miss src/Shared/BuildingBlocks/Logging/SerilogLoggingExtensions.cs:96β `UseSerilogReqLogging` reads `app.Configuration.GetValue($"{section}:{SerilogCfg.Enable}", false)` β a missing or misspelt key silently becomes `false`, with no log or throw. Validate the options at startup (or log the miss); if that constant is the specified default, document it on the member and the row stops firing.
Silent fallback default in catch src/Services/Catalog/Core/Catalog.Infrastructure/Data/InitialData.cs:54β `Populate` swallows every exception into `return false;` β a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/JobOrchestrator/App.Job/Quartz/JobRegistrationExtensions.cs:98β `DiscoverJobTypes` swallows every exception into `return new List<Type>();` β a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/JobOrchestrator/App.Job/Quartz/JobRegistrationExtensions.cs:119β `GetJobTypesFromAssembly` swallows `ReflectionTypeLoadException` into `return new List<Type>();` β a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Pass-through layer src/Services/Inventory/Core/Inventory.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:10β DbTransactionAdapter: all 4 public methods forward their arguments unchanged to transaction and add no behaviour β an extra hop (and usually an extra interface) to trace through. Call transaction directly, or give the layer a job.
Pass-through layer src/Services/Order/Core/Order.Infrastructure/UnitOfWork/DbTransactionAdapter.cs:10β DbTransactionAdapter: all 4 public methods forward their arguments unchanged to transaction and add no behaviour β an extra hop (and usually an extra interface) to trace through. Call transaction directly, or give the layer a job.
Partial audit-trail evidence β An audit mechanism is present, but the trail is not yet complete β missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
D16 Β· Bus FactorΒ· Small-team knowledge concentration Β· Γ1
Small-team knowledge concentration β 1 file(s) are concentrated to one author β the ambient state with 2 active author(s), not 1 separate risks. The signal becomes meaningful as ownership spreads; no per-file action implied now.
No ADRs found β No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these β unnumbered files outside any recognised directory, without those headings β is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D28 Β· Secrets (history)Β· Rotate the exposed credentials Β· Γ1
REDACTED
D34 Β· Knowledge FreshnessΒ· Further orphaned files (smaller) Β· Γ1
Further orphaned files (smaller) β 22 smaller file(s) also have no living knowledge β folded into the freshness score and metrics rather than raised one row each β most significant first: src/JobOrchestrator/App.Job/Jobs/Report/SyncDashboardReportJob.cs, src/Services/Inventory/Worker/Inventory.Worker.Consumer/EventHandlers/Integrations/OrderCreatedIntegrationEventHandler.cs, src/JobOrchestrator/App.Job/DependencyInjection.cs, src/JobOrchestrator/App.Job/Quartz/JobRegistrationExtensions.cs, src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.cs, src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/Commands/UpdateInventoryItemCommand.cs, src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderStatusCommand.cs, src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/Commands/ReserveInventoryCommand.cs (and 14 more) (23 orphaned of 117 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 117 of the 916 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
IL efficiency: 11 authored method(s) exceed the IL budget src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17β 11 of 2417 first-party methods compile to oversized IL bodies (> 250 instructions); worst: Inventory.Infrastructure.Data.Configurations.OutboxMessageConfiguration.Configure @ src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17, 499 IL instructions; that pulled this dimension to 9.9/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable β what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
No tests found β No test suite could be collected β no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
DM9 Β· Scattered domain decisionsΒ· Rule about [ReferenceId, Status] decided in 2 places Β· Γ1
Rule about [ReferenceId, Status] decided in 2 places β Inventory.Domain.Entities.InventoryReservationEntity's [ReferenceId, Status] are judged in Inventory.Application.Features.InventoryReservation.Commands.CommitReservationCommandHandler, Inventory.Application.Features.InventoryReservation.Commands.ReleaseReservationCommandHandler β 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.
DM9 Β· Scattered domain decisionsΒ· Rule about [MaxUsage, Status, UsageCount, ValidFrom, ValidTo] decided in 2 places Β· Γ1
Rule about [MaxUsage, Status, UsageCount, ValidFrom, ValidTo] decided in 2 places β Discount.Domain.Entities.CouponEntity's [MaxUsage, Status, UsageCount, ValidFrom, ValidTo] are judged in Discount.Infrastructure.Data.Extensions.DatabaseExtentions, Discount.Infrastructure.Repositories.CouponRepository β 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.
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.
Inconsistent root namespaces β Only 8/58 projects share a common root namespace β the code's module identity is inconsistent.
P2 Β· ObservabilityΒ· Logging is not universal Β· Γ1
Logging is not universal β Only 38/45 service-like projects use logging (pure contract/DTO projects are excluded β they have nothing to log). Of those 45, 15 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P3 Β· Security & performance toolingΒ· No SAST Β· Γ1
No SAST REDACTED:4β No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 77652 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen β if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation REDACTED:9β `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices β including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
PF1 Β· Benchmark disciplineΒ· No performance benchmarks Β· Γ1
No performance benchmarks β No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file β every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks β a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions β but it's a bonus here, not a deduction.
X2 Β· Cancellation propagationΒ· Not all async methods take a CancellationToken Β· Γ1
Not all async methods take a CancellationToken β Only 297/392 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up β whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice β judge against your hosting model.
Null-forgiving operator (`!`) suppressions reduce the NRT score β ~2.8 `!` suppressions per 1k syntax nodes β 420 suppression(s) across the 150754 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Silent fallback default on parse failure src/Shared/BuildingBlocks/Logging/SerilogLoggingExtensions.cs:129β `ParseLevel` falls back to `LogEventLevel.Information` when `Enum.TryParse<LogEventLevel>(s, true, out var lvl)` is false, with no log or throw β a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
doc comments repeat the names src/Shared/BuildingBlocks/Validators/CustomValidators.cs:24β 2 of 3 documented parameters and 0 of 2 summaries in `BuildingBlocks` only repeat the member or parameter name (e.g. "The rule builder" for `ruleBuilder`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Services/Discount/Core/Discount.Application/Repositories/IUnitOfWork.cs:23β 4 of 4 documented parameters and 2 of 6 summaries in `Discount.Application` only repeat the member or parameter name (e.g. "Begins a new transaction." for `BeginTransactionAsync`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Services/Discount/Core/Discount.Infrastructure/Repositories/UnitOfWork.cs:58β 0 of 0 documented parameters and 1 of 9 summaries in `Discount.Infrastructure` only repeat the member or parameter name (e.g. "Commits the current transaction." for `CommitTransactionAsync`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Apps/App.Admin/src/services/catalogService.js:30β 25 of 75 documented parameters and 36 of 89 summaries in `dashkit-react-kitp` only repeat the member or parameter name (e.g. "Get product by ID" for `getProductById`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Apps/App.Store/src/services/basketService.js:28β 5 of 37 documented parameters and 11 of 37 summaries in `farzaa-react` only repeat the member or parameter name (e.g. "Checkout basket" for `checkoutBasket`). Delete the restating tags, or add what the name does not say.
Off the main sequence: Common REDACTED:1β Common: 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: BuildingBlocks REDACTED:1β BuildingBlocks: abstractness 0.23, instability 0.07, distance 0.70 β 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.
Shared: 1 contract type(s) expose producer-owned ids/enums β In Shared, 1 contract type(s) (DeletedUnPublishedProductIntegrationEvent) expose strong-typed ids/value objects (DeletedUnPublishedProductIntegrationEvent); a serialized contract could expose the underlying primitive instead. Advisory β a deliberate strong-ID style is fine.
Appendix B β Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension β the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative β never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json β kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 167 file(s) β `src/JobOrchestrator/App.Job/GrpcClients/Interceptors/GrpcApiKeyInterceptor.cs`, `src/JobOrchestrator/App.Job/Jobs/Inventory/ExpireInventoryReservationsJob.cs`, `src/JobOrchestrator/App.Job/Jobs/Report/SyncDashboardReportJob.cs`, `src/JobOrchestrator/App.Job/Quartz/QuartzHostedService.cs`, `src/Services/Basket/Core/Basket.Application/Features/Basket/Commands/BasketCheckoutCommand.cs`, β¦ (+162 more) β so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable β No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1be27-309e-78ce-9644-c489950aea0d Β· 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 β 30 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: 775 Β· Warnings: 893 Β· Recommendations: 332 Β· Info: 63 β Appendix A Β· all findings Β· full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 09-11-2026 @ 02:33 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.