Public report — progcoder-shop-microservices, published 21 Sep 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.15 (frozen) · verify this surveyFiledcd_097b61468bbb4ff6a3e149e41a1f99cd
Filed 25 September 2026, 05:09 UTC
Public
Large · 102,573 LoC · 58 projects · rebuild ~1.2 person-years · weakest lens: Readiness (16%)
Findings by grade
536 critical666 serious504 minor5 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 September 2026, 16:37 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
1337findings with an exact file:lineof 1706 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
115/140dimensions across the health lenses102573 LoC · 58 projects — wide & deep
⚠ A critical security finding caps this grade — resolve it before relying on the score below; see the Security lens.
This system is a large, high-value asset carrying significant operational risk, reflected in an overall health score of 29%. With over 100,000 lines of production code and a rebuild cost nearing €180,000, the business has substantial capital tied up here. However, the system is fragile in practice. While the underlying architecture is sound, the lack of operational readiness and security controls means that every change carries a hidden tax on speed and reliability. The biggest issue is trust boundaries: the system lacks automated security checks and basic testing, leaving it exposed to regressions and defects that could disrupt service or compromise data. This is not a minor technical debt; it is a structural vulnerability that threatens delivery velocity and customer trust.
The second major theme is an un-encapsulated domain model. The code relies heavily on simple, straight-line logic with minimal branching, but the domain objects do not protect their own rules. This leads to widespread complexity and duplication, as developers must manually enforce constraints in scattered places. This pattern acts as a velocity tax, plausibly increasing the cost of every change by 2–5%. Over time, this compounds, making the system harder and more expensive to modify as it grows. The root cause is not individual bugs, but a design pattern that fails to encapsulate business logic, forcing teams to chase symptoms rather than fixing the source.
What is genuinely good is the architectural foundation. The system is well-structured, with clear separation of concerns and a mature event-driven design that supports scalability. The code is largely boilerplate and straightforward logic, which is easy to read but difficult to test without significant refactoring. The primary focus should be on adding a static analysis step to the continuous integration pipeline. This single action would catch security regressions before they reach production, providing immediate protection with minimal effort. It is the highest-leverage move, paying for itself quickly by preventing costly outages and security incidents. Other improvements, such as refactoring the domain model, should follow once the operational baseline is secure. The picture is partial, as event sourcing and accessibility were not measured, but the current risks are clear and actionable.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
0.7× (at 29% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified for 74,866 line(s) outside the .NET model (the tier breakdown is a C#-only syntax walk)
Dead frontend code
~26284 LoC unreachable (203 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~1.2 person-years of build effort (about ~€180,000 to rebuild). Its weakest lens is Readiness at 16% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Very high (×2.1) — microservices, DDD/clean architecture, CQRS, domain model, event-driven integration × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 6 Deprecated finding(s) in Dependency Hygiene.
Value concentrated against a weak lens · REDACTED · Value at risk
This is a Large asset (~1.2 person-years to rebuild), and its weakest lens is Readiness at 16%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Root cause: an un-encapsulated domain · REDACTED · Root cause
58 findings across public setters, anemic types and primitive ids share one root cause — the domain layer doesn't protect its own invariants. Fixing the encapsulation pattern resolves them together, rather than chasing each finding.
→ Address encapsulation as one pattern (private setters + behaviour + strongly-typed ids), not 100 separate findings.
Highest-leverage move · REDACTED · Leverage
Of everything flagged, the best return on effort is: 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. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ 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.
A velocity tax on every change · REDACTED · Economics
The code-quality signals (complexity, duplication, cohesion) average 7.2/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 2–5% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4/D6 code quality: averaging 7.2/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
The top fix pays for itself · REDACTED · Economics
The top-ranked fix costs roughly 1–3 engineer-days once. Not doing it costs about 0.1–0.7 engineer-days every year, paid as drag on the ~2,121 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 17–339 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 2–5% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 523 line(s) changed over a 90-day window ⇒ ~2,121/year · D1/D2/D4/D6 code quality: averaging 7.2/10 ⇒ a 2–5% drag on each change · top-ranked remediation: Low effort ⇒ about 1–3 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 339 months.
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 — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
477 modules, 413 dependencies. 2 dependency cycles across 6 modules, marked above the diagonal.
Showing the 40 most-connected modules; 437 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
Basket.Application.Repositories uses Basket.Domain.Entities. Changing Basket.Domain.Entities can break Basket.Application.Repositories, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
17→5 BuildingBlocks.Pagination depends on Common.Models✕
Type pairs
1 distinct (type in BuildingBlocks.Pagination → type in Common.Models) reference.
Discount.Application.Dtos.Coupons uses Discount.Domain.Enums. Changing Discount.Domain.Enums can break Discount.Application.Dtos.Coupons, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
21→7 Discount.Application.Repositories depends on Discount.Domain.Enums✕
Type pairs
2 distinct (type in Discount.Application.Repositories → type in Discount.Domain.Enums) references.
Discount.Application.Repositories uses Discount.Domain.Enums. Changing Discount.Domain.Enums can break Discount.Application.Repositories, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
22→9 Inventory.Domain.Entities depends on Inventory.Domain.Abstractions✕
Type pairs
6 distinct (type in Inventory.Domain.Entities → type in Inventory.Domain.Abstractions) references.
Inventory.Domain.Entities uses Inventory.Domain.Abstractions. Changing Inventory.Domain.Abstractions can break Inventory.Domain.Entities, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
23→10 Notification.Application.Data.Repositories depends on Notification.Domain.Enums✕
Type pairs
1 distinct (type in Notification.Application.Data.Repositories → type in Notification.Domain.Enums) reference.
Notification.Application.Data.Repositories uses Notification.Domain.Enums. Changing Notification.Domain.Enums can break Notification.Application.Data.Repositories, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
24→2 Order.Application.Features.Order.Commands depends on BuildingBlocks.CQRS✕
Type pairs
6 distinct (type in Order.Application.Features.Order.Commands → type in BuildingBlocks.CQRS) references.
Order.Application.Features.Order.Commands uses BuildingBlocks.CQRS. Changing BuildingBlocks.CQRS can break Order.Application.Features.Order.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
24→6 Order.Application.Features.Order.Commands depends on Common.ValueObjects✕
Type pairs
3 distinct (type in Order.Application.Features.Order.Commands → type in Common.ValueObjects) references.
Order.Application.Features.Order.Commands uses Common.ValueObjects. Changing Common.ValueObjects can break Order.Application.Features.Order.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
24→11 Order.Application.Features.Order.Commands depends on Order.Application.Dtos.Orders✕
Type pairs
2 distinct (type in Order.Application.Features.Order.Commands → type in Order.Application.Dtos.Orders) references.
Order.Application.Features.Order.Commands uses Order.Application.Dtos.Orders. Changing Order.Application.Dtos.Orders can break Order.Application.Features.Order.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
24→12 Order.Application.Features.Order.Commands depends on Order.Domain.Abstractions✕
Type pairs
3 distinct (type in Order.Application.Features.Order.Commands → type in Order.Domain.Abstractions) references.
Order.Application.Features.Order.Commands uses Order.Domain.Abstractions. Changing Order.Domain.Abstractions can break Order.Application.Features.Order.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
25→12 Order.Domain.Entities depends on Order.Domain.Abstractions✕
Type pairs
4 distinct (type in Order.Domain.Entities → type in Order.Domain.Abstractions) references.
Catalog.Application.Features.Product.Commands uses BuildingBlocks.CQRS. Changing BuildingBlocks.CQRS can break Catalog.Application.Features.Product.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→3 Catalog.Application.Features.Product.Commands depends on Catalog.Domain.Entities✕
Type pairs
2 distinct (type in Catalog.Application.Features.Product.Commands → type in Catalog.Domain.Entities) references.
Catalog.Application.Features.Product.Commands uses Catalog.Domain.Entities. Changing Catalog.Domain.Entities can break Catalog.Application.Features.Product.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→5 Catalog.Application.Features.Product.Commands depends on Common.Models✕
Type pairs
2 distinct (type in Catalog.Application.Features.Product.Commands → type in Common.Models) references.
Catalog.Application.Features.Product.Commands uses Common.Models. Changing Common.Models can break Catalog.Application.Features.Product.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→6 Catalog.Application.Features.Product.Commands depends on Common.ValueObjects✕
Type pairs
5 distinct (type in Catalog.Application.Features.Product.Commands → type in Common.ValueObjects) references.
Catalog.Application.Features.Product.Commands uses Common.ValueObjects. Changing Common.ValueObjects can break Catalog.Application.Features.Product.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→18 Catalog.Application.Features.Product.Commands depends on Catalog.Application.Dtos.Products✕
Type pairs
2 distinct (type in Catalog.Application.Features.Product.Commands → type in Catalog.Application.Dtos.Products) references.
Catalog.Application.Features.Product.Commands uses Catalog.Application.Dtos.Products. Changing Catalog.Application.Dtos.Products can break Catalog.Application.Features.Product.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→5 Catalog.Application.Models.Results depends on Common.Models✕
Type pairs
2 distinct (type in Catalog.Application.Models.Results → type in Common.Models) references.
Catalog.Application.Models.Results uses BuildingBlocks.Pagination. Changing BuildingBlocks.Pagination can break Catalog.Application.Models.Results, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→18 Catalog.Application.Models.Results depends on Catalog.Application.Dtos.Products✕
Type pairs
6 distinct (type in Catalog.Application.Models.Results → type in Catalog.Application.Dtos.Products) references.
Catalog.Application.Models.Results uses Catalog.Application.Dtos.Products. Changing Catalog.Application.Dtos.Products can break Catalog.Application.Models.Results, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
29→2 Discount.Application.Features.Coupon.Commands depends on BuildingBlocks.CQRS✕
Type pairs
16 distinct (type in Discount.Application.Features.Coupon.Commands → type in BuildingBlocks.CQRS) references.
Discount.Application.Features.Coupon.Commands uses BuildingBlocks.CQRS. Changing BuildingBlocks.CQRS can break Discount.Application.Features.Coupon.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
29→6 Discount.Application.Features.Coupon.Commands depends on Common.ValueObjects✕
Type pairs
5 distinct (type in Discount.Application.Features.Coupon.Commands → type in Common.ValueObjects) references.
Discount.Application.Features.Coupon.Commands uses Common.ValueObjects. Changing Common.ValueObjects can break Discount.Application.Features.Coupon.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
29→20 Discount.Application.Features.Coupon.Commands depends on Discount.Application.Dtos.Coupons✕
Type pairs
5 distinct (type in Discount.Application.Features.Coupon.Commands → type in Discount.Application.Dtos.Coupons) references.
Discount.Application.Features.Coupon.Commands uses Discount.Application.Dtos.Coupons. Changing Discount.Application.Dtos.Coupons can break Discount.Application.Features.Coupon.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
29→21 Discount.Application.Features.Coupon.Commands depends on Discount.Application.Repositories✕
Type pairs
8 distinct (type in Discount.Application.Features.Coupon.Commands → type in Discount.Application.Repositories) references.
Discount.Application.Features.Coupon.Commands uses Discount.Application.Repositories. Changing Discount.Application.Repositories can break Discount.Application.Features.Coupon.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
30→5 Inventory.Application.Models.Results depends on Common.Models✕
Type pairs
1 distinct (type in Inventory.Application.Models.Results → type in Common.Models) reference.
Inventory.Application.Models.Results uses BuildingBlocks.Pagination. Changing BuildingBlocks.Pagination can break Inventory.Application.Models.Results, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→8 Inventory.Application.Services depends on Inventory.Application.Models.Responses.Externals✕
Type pairs
2 distinct (type in Inventory.Application.Services → type in Inventory.Application.Models.Responses.Externals) references.
Inventory.Application.Services uses Inventory.Application.Models.Responses.Externals. Changing Inventory.Application.Models.Responses.Externals can break Inventory.Application.Services, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
31→19 Inventory.Application.Services depends on Common.Models.Reponses✕
Type pairs
1 distinct (type in Inventory.Application.Services → type in Common.Models.Reponses) reference.
Notification.Application.Features.Delivery.Commands uses BuildingBlocks.CQRS. Changing BuildingBlocks.CQRS can break Notification.Application.Features.Delivery.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→6 Notification.Application.Features.Delivery.Commands depends on Common.ValueObjects✕
Type pairs
2 distinct (type in Notification.Application.Features.Delivery.Commands → type in Common.ValueObjects) references.
Notification.Application.Features.Delivery.Commands uses Common.ValueObjects. Changing Common.ValueObjects can break Notification.Application.Features.Delivery.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→23 Notification.Application.Features.Delivery.Commands depends on Notification.Application.Data.Repositories✕
Type pairs
5 distinct (type in Notification.Application.Features.Delivery.Commands → type in Notification.Application.Data.Repositories) references.
Notification.Application.Features.Delivery.Commands uses Notification.Application.Data.Repositories. Changing Notification.Application.Data.Repositories can break Notification.Application.Features.Delivery.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
33→5 Order.Api.Endpoints depends on Common.Models✕
Type pairs
2 distinct (type in Order.Api.Endpoints → type in Common.Models) references.
Order.Application.Features.Order.Queries uses BuildingBlocks.CQRS. Changing BuildingBlocks.CQRS can break Order.Application.Features.Order.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→5 Order.Application.Features.Order.Queries depends on Common.Models✕
Type pairs
2 distinct (type in Order.Application.Features.Order.Queries → type in Common.Models) references.
Order.Application.Features.Order.Queries uses Common.Models. Changing Common.Models can break Order.Application.Features.Order.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→6 Order.Application.Features.Order.Queries depends on Common.ValueObjects✕
Type pairs
3 distinct (type in Order.Application.Features.Order.Queries → type in Common.ValueObjects) references.
Order.Application.Features.Order.Queries uses Common.ValueObjects. Changing Common.ValueObjects can break Order.Application.Features.Order.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→12 Order.Application.Features.Order.Queries depends on Order.Domain.Abstractions✕
Type pairs
8 distinct (type in Order.Application.Features.Order.Queries → type in Order.Domain.Abstractions) references.
Order.Application.Features.Order.Queries uses Order.Domain.Abstractions. Changing Order.Domain.Abstractions can break Order.Application.Features.Order.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→25 Order.Application.Features.Order.Queries depends on Order.Domain.Entities✕
Type pairs
1 distinct (type in Order.Application.Features.Order.Queries → type in Order.Domain.Entities) reference.
Order.Application.Features.Order.Queries uses Order.Domain.Entities. Changing Order.Domain.Entities can break Order.Application.Features.Order.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→8 Refit.Implementation depends on Inventory.Application.Models.Responses.Externals✕
Type pairs
2 distinct (type in Refit.Implementation → type in Inventory.Application.Models.Responses.Externals) references.
Refit.Implementation uses Inventory.Application.Models.Responses.Externals. Changing Inventory.Application.Models.Responses.Externals can break Refit.Implementation, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→19 Refit.Implementation depends on Common.Models.Reponses✕
Type pairs
1 distinct (type in Refit.Implementation → type in Common.Models.Reponses) reference.
Catalog.Api.Endpoints uses Catalog.Application.Models.Results. Changing Catalog.Application.Models.Results can break Catalog.Api.Endpoints, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→5 Inventory.Api.Endpoints depends on Common.Models✕
Type pairs
1 distinct (type in Inventory.Api.Endpoints → type in Common.Models) reference.
Inventory.Api.Endpoints uses Inventory.Application.Models.Results. Changing Inventory.Application.Models.Results can break Inventory.Api.Endpoints, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→2 Inventory.Application.Features.InventoryItem.Commands depends on BuildingBlocks.CQRS✕
Type pairs
8 distinct (type in Inventory.Application.Features.InventoryItem.Commands → type in BuildingBlocks.CQRS) references.
Inventory.Application.Features.InventoryItem.Commands uses BuildingBlocks.CQRS. Changing BuildingBlocks.CQRS can break Inventory.Application.Features.InventoryItem.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→6 Inventory.Application.Features.InventoryItem.Commands depends on Common.ValueObjects✕
Type pairs
4 distinct (type in Inventory.Application.Features.InventoryItem.Commands → type in Common.ValueObjects) references.
Inventory.Application.Features.InventoryItem.Commands uses Common.ValueObjects. Changing Common.ValueObjects can break Inventory.Application.Features.InventoryItem.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→9 Inventory.Application.Features.InventoryItem.Commands depends on Inventory.Domain.Abstractions✕
Type pairs
4 distinct (type in Inventory.Application.Features.InventoryItem.Commands → type in Inventory.Domain.Abstractions) references.
Inventory.Application.Features.InventoryItem.Commands uses Inventory.Domain.Abstractions. Changing Inventory.Domain.Abstractions can break Inventory.Application.Features.InventoryItem.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→31 Inventory.Application.Features.InventoryItem.Commands depends on Inventory.Application.Services✕
Type pairs
4 distinct (type in Inventory.Application.Features.InventoryItem.Commands → type in Inventory.Application.Services) references.
Inventory.Application.Features.InventoryItem.Commands uses Inventory.Application.Services. Changing Inventory.Application.Services can break Inventory.Application.Features.InventoryItem.Commands, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→2 Inventory.Application.Features.InventoryItem.Queries depends on BuildingBlocks.CQRS✕
Type pairs
4 distinct (type in Inventory.Application.Features.InventoryItem.Queries → type in BuildingBlocks.CQRS) references.
Inventory.Application.Features.InventoryItem.Queries uses BuildingBlocks.CQRS. Changing BuildingBlocks.CQRS can break Inventory.Application.Features.InventoryItem.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→5 Inventory.Application.Features.InventoryItem.Queries depends on Common.Models✕
Type pairs
1 distinct (type in Inventory.Application.Features.InventoryItem.Queries → type in Common.Models) reference.
Inventory.Application.Features.InventoryItem.Queries uses Common.Models. Changing Common.Models can break Inventory.Application.Features.InventoryItem.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→9 Inventory.Application.Features.InventoryItem.Queries depends on Inventory.Domain.Abstractions✕
Type pairs
2 distinct (type in Inventory.Application.Features.InventoryItem.Queries → type in Inventory.Domain.Abstractions) references.
Inventory.Application.Features.InventoryItem.Queries uses Inventory.Domain.Abstractions. Changing Inventory.Domain.Abstractions can break Inventory.Application.Features.InventoryItem.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→30 Inventory.Application.Features.InventoryItem.Queries depends on Inventory.Application.Models.Results✕
Type pairs
2 distinct (type in Inventory.Application.Features.InventoryItem.Queries → type in Inventory.Application.Models.Results) references.
Inventory.Application.Features.InventoryItem.Queries uses Inventory.Application.Models.Results. Changing Inventory.Application.Models.Results can break Inventory.Application.Features.InventoryItem.Queries, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→4 Inventory.Infrastructure.Services depends on Catalog.Grpc✕
Type pairs
1 distinct (type in Inventory.Infrastructure.Services → type in Catalog.Grpc) reference.
Inventory.Infrastructure.Services uses Inventory.Application.Models.Responses.Externals. Changing Inventory.Application.Models.Responses.Externals can break Inventory.Infrastructure.Services, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→19 Inventory.Infrastructure.Services depends on Common.Models.Reponses✕
Type pairs
1 distinct (type in Inventory.Infrastructure.Services → type in Common.Models.Reponses) reference.
Inventory.Infrastructure.Services uses Common.Models.Reponses. Changing Common.Models.Reponses can break Inventory.Infrastructure.Services, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→31 Inventory.Infrastructure.Services depends on Inventory.Application.Services✕
Type pairs
2 distinct (type in Inventory.Infrastructure.Services → type in Inventory.Application.Services) references.
Inventory.Infrastructure.Services uses Inventory.Application.Services. Changing Inventory.Application.Services can break Inventory.Infrastructure.Services, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
At a glance — Code Health · 44% · Weak · gated by D3, 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
A03:2021 — Injection
258
REDACTED / Critical
A02:2021 — Cryptographic Failures
110
REDACTED / Critical
A05:2021 — Security Misconfiguration
81
REDACTED / Critical
A06:2021 — Vulnerable & Outdated Components
77
REDACTED / Critical
Roadmap
First, integrate a security analysis step into the CI pipeline to prevent security regressions from merging, and immediately resolve the 26 leaked secrets found in configuration files. Next, refactor entry-point modules to be importable by tests to establish baseline coverage, while cleaning up the dependency list by removing unused packages and addressing deprecated warnings. Finally, ensure all remaining production modules are directly testable through their public entries to close the coverage gap.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 Deprecated finding(s) in Dependency Hygiene.
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.
14 of the 644 unreached modules are entry points — the browser loads some as a top-level script and something else executes the rest by path, so no import specifier addresses them and no public entry publishes them. An importing test cannot be written for them as they ship, and two different things are worth doing here — they are not the same thing. To EXERCISE them, a browser or end-to-end suite that loads the page, or a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make them addressable: lift the logic into a module a test can import and leave the entry points thin shims over it, or put their bodies behind a main-guard (`import.meta.url === argv[1]`) and export them. Add tests that import the other 630 — directly or through their public entry.
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 — 536
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 — 666
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 — 504
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 110 of 115 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 115 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1337 of 1706 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 10 deducted marker(s) and the 0.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .jsx (67,192 lines, 66% 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.
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.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. At 27172 LoC across 58 projects this is a very large multi-module system that clearly needs explicit bounded contexts. Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (go.mod, a Gemfile's ruby directive, a REDACTED) is simply not read here yet.
AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 419 further occurrence(s) are not listed individually; the score already reflects all 459.
AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Both arms resolve expressions to symbols (a comparison operand to the member it judges, a construction to the type it constructs) and that resolution comes from a Roslyn compilation, which this run has for the C#/VB projects only. The other languages in this repository were not walked for this dimension, so the counts above speak for part of the codebase.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 47 further occurrence(s) are not listed individually; the score already reflects all 87.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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 judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
The LLM boundary
LLM-set scores this run (5): D19, D21, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
45 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.
+ 36 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 keycloakService.getUserInfo (cyclomatic 31) finding(s) in Cyclomatic Complexity — start with keycloakService.js (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 index.InventoryPage (cyclomatic 171) finding(s) in Cyclomatic Complexity — start with index.jsx. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 index.CouponPage (cyclomatic 128) finding(s) in Cyclomatic Complexity — start with index.jsx. — One of this dimension's main actionable groups (1 warning-level).
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.
+ 41 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 getUserInfo (cognitive 31) finding(s) in Cognitive Complexity — start with keycloakService.js (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 index.InventoryPage (cognitive 163) finding(s) in Cognitive Complexity — start with index.jsx. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FarzaaContext.FarzaaContextProvider (cognitive 147) finding(s) in Cognitive Complexity — start with FarzaaContext.jsx. — One of this dimension's main actionable groups (1 warning-level).
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 134 FunctionTooLong finding(s) in God Classes — start with index.jsx (15), KeycloakContext.jsx (2), FarzaaContext.jsx. — One of this dimension's main actionable groups (134 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 (66% 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.
+ 72 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), OutboxMessageEntity.cs, OutboxProcessor.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with StringExtension.cs, ReservationCommittedDomainEventHandler.cs, ICatalogGrpcService.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 3 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 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.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
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, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
59 outdated, 3 vulnerable, 6 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 234 outdated of 378 package(s) across 2 lockfile(s).
Resolve the 6 Deprecated finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 issue-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 26 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (23), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (26 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.
10 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.
Banned license: MySql.Data · ×10
What to do
Resolve the 10 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (10 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: 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.
6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Services/Order/Core/Order.Application/Features/Order/Commands/UpdateOrderCommand.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 + 0 dead symbols across 27172 LoC in the .NET projects (0.1/KLoC) → score 9.7. Measured on the .NET source only: .jsx (66% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
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 2 Whole file has no live code finding(s) in Explicit Debt — start with UnitOfWorkUsageExample.cs, CatalogGrpcService.cs. — One of this dimension's main actionable groups (2 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), 230 inter-project edges.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The ProG Coder Shop microservices project has a strong README with an extensive table of contents and a clear overview of the architecture (Clean Architecture, DDD, CQRS, event-driven), plus prerequisites, environment configuration, and a quick start for production/testing mode. The document is well-organized into numbered sections covering technology stack, design patterns, infrastructure, microservices, web apps, observability, and CI/CD, with many cross-project links to tutorials, support, and the GitHub star page. However it lacks installation/build instructions (missing-installation) and a dedicated architecture/design docs section for the other services in the suite.
Documentation: no installation or build instructionsREADME.md
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
2 naming inconsistencies across 200 sampled symbols.
The class name 'DatabaseExtentions' contains a spelling error ('Extentions' instead of 'Extensions'). This misspelling is consistently applied to the type and its members, but it represents a deviation from the standard English spelling convention for this common technical term.
The word 'Response' is misspelled as 'Reponse' in two different locations: 'ProductReponse' and 'ApiUpdatedResponse'. This indicates a systematic typo in the codebase's naming for response models.
What to do
Resolve the 1 The class name 'DatabaseExtentions' contains a spelling error… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 The word 'Response' is misspelled as 'Reponse' in two different… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueStrong◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
Resolve the 3 redundant comment finding(s) in Comment Value — start with Program.cs, JobRegistrationExtensions.cs, DependencyInjection.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
0 of 58 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability8.9 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
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.
What to do
Improve Navigability — currently 8.9/10. — 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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged REDACTED. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
83 finding(s): 0 critical, 83 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 64 REDACTED finding(s) in Secrets (history) — start with REDACTED (39), REDACTED (17), REDACTED (5). — One of this dimension's main actionable groups (64 issue-level).
Resolve the 19 REDACTED secret finding(s) in Secrets (history) — start with REDACTED (10), REDACTED (9). — One of this dimension's main actionable groups (19 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).
258 finding(s): 0 critical, 256 high, 2 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
What to do
Resolve the 28 REDACTED finding(s) charged to Static Analysis (SAST) — the other 228 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (256 issue-level, 28 of them charged here).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir/Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex, Go, Java and Kotlin via Maven/Gradle, npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 52 REDACTED CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (30), REDACTED (10). — One of this dimension's main actionable groups (52 issue-level).
Resolve the 5 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 15 REDACTED CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED. — One of this dimension's main actionable groups (15 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 56 REDACTED 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 REDACTED 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.
21 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 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.
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. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
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). (×26) — 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. — src/Apps/App.Admin/src/components/partials/header/Tools/SearchModal.jsx:89
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: interactive elements plus elements the markup gives a click/key handler or the repo's own CSS styles `cursor: pointer`, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element 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.
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. (×5) — src/Apps/App.Admin/src/components/partials/ecommerce/steps/cart-step.jsx:105, src/Apps/App.Admin/src/pages/auth/forgot-password.jsx:53, src/Apps/App.Admin/src/pages/auth/forgot-password2.jsx:33, …
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 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.
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.
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. 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.7 / 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), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain8.9 / 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:32
`BrandEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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:21
`CategoryEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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:25
`CouponEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `Update`, `Approve`, `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:42
`DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateCount`, `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:27
`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:32
`DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateStatus`, `RaiseError`. 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/Notification/Core/Notification.Domain/Entities/DeliveryEntity.cs:38
`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:65
`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:19
`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:34
`InventoryItemEntity` reads `DateTimeOffset.UtcNow` inside `Update`, `Decrease`, `Reserve`, `Unreserve`. 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:72
`InventoryReservationEntity` reads `DateTimeOffset.UtcNow` inside `MarkCommitted`, `Release`, `Expire`. 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/InventoryReservationEntity.cs:69
`LocationEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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/LocationEntity.cs:19
`NotificationEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `MarkAsRead`, `UpdateTargetUrl`. 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/Notification/Core/Notification.Domain/Entities/NotificationEntity.cs:32
`OrderCancelledDomainEventHandler` 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/Order/Core/Order.Application/Features/Order/EventHandlers/Domain/OrderCancelledDomainEventHandler.cs:32
`OrderCreatedDomainEventHandler` 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/Order/Core/Order.Application/Features/Order/EventHandlers/Domain/OrderCreatedDomainEventHandler.cs:34
`OrderDeliveredDomainEventHandler` 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/Order/Core/Order.Application/Features/Order/EventHandlers/Domain/OrderDeliveredDomainEventHandler.cs:32
`OrderEntity` reads `DateTimeOffset.UtcNow` inside `UpdateShippingAddress`, `UpdateCustomerInfo`, `UpdateStatus`, `CancelOrder`. 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/Order/Core/Order.Domain/Entities/OrderEntity.cs:86
`OrderGrowthLineChartEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateValue`. 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/OrderGrowthLineChartEntity.cs:23
`OrderNo` reads `DateTimeOffset.Now` 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/Order/Core/Order.Domain/ValueObjects/OrderNo.cs:19
`OutboxMessageEntity` 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. (×4) — src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:73, src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:73, src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs:65, …
`ProductEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `Update`, `Publish`, `Unpublish`. 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/ProductEntity.cs:64
`ProductEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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/Search/Core/Search.Domain/Entities/ProductEntity.cs:36
`ReservationExpiredDomainEventHandler` 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/InventoryReservation/EventHandlers/Domain/ReservationExpiredDomainEventHandler.cs:45
`StockChangedDomainEventHandler` 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/StockChangedDomainEventHandler.cs:34
`TemplateEntity` 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/Notification/Core/Notification.Domain/Entities/TemplateEntity.cs:28
`TopProductPieChartEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateValue`. 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/TopProductPieChartEntity.cs:21
`UpsertedProductDomainEventHandler` 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/UpsertedProductDomainEventHandler.cs:32
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.
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
`InventoryItemRepository` is a repository over `InventoryItemEntity`, 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 `InventoryItemEntity` through its owning aggregate instead. — src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/InventoryItemRepository.cs:15
`InventoryReservationRepository` is a repository over `InventoryReservationEntity`, 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 `InventoryReservationEntity` through its owning aggregate instead. — src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/InventoryReservationRepository.cs:12
`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
`OrderRepository` is a repository over `OrderEntity`, 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 `OrderEntity` through its owning aggregate instead. — src/Services/Order/Core/Order.Infrastructure/Repositories/OrderRepository.cs:15
What to do
Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
The parameters [content, eventtype, id] travel together across 6 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:35
The parameters [attemptcount, lasterrormessage, maxattempts] travel together across 5 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:65
The parameters [addressline, city, country, postalcode, stateorprovince, subdivision] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — src/Services/Order/Core/Order.Domain/ValueObjects/Address.cs:37
The parameters [email, id, name, phonenumber] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules. — src/Services/Order/Core/Order.Domain/ValueObjects/Customer.cs:27
What to do
Extract recurring primitive parameter clusters into value objects so the concept (and its rules) lives in one place.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
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.
Order.Domain.Enums.OrderStatus's [Canceled, Delivered, Refunded] are judged in Order.Application.Features.Order.Commands.UpdateOrderCommandHandler, Order.Application.Features.Order.Commands.UpdateOrderStatusCommandHandler — 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.
`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.
`CreateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:66
`PublishProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/PublishProductCommand.cs:37
`UpdateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). — src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:67
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.
Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.
`Commands.CreateLocationCommandHandler.Handle` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Services/Inventory/Core/Inventory.Application/Features/Location/Commands/CreateLocationCommand.cs:38
`Commands.DeleteProductCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Services/Search/Core/Search.Application/Features/Product/Commands/DeleteProductCommand.cs:18
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
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×38) — 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
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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
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.
No test surface was found — this check walked the tree for authored source in the languages it models (`.cs`, `.vb`, `.fs`, `.java`, `.kt`, `.scala`, `.py`, `.php`, `.rb`, `.ex`, `.exs`, `.go`, `.erl`, `.hrl`, `.swift`, `.dart`, `.rs`, `.ts`, `.tsx`, `.mts`, `.cts`) and found none of it test-shaped. ★ `.js`, `.jsx`, `.mjs` and `.cjs` are NOT in that walk, so a Jest or Mocha suite written in plain JavaScript is invisible to it and this row is then wrong. If that is your case, say so rather than moving anything. Otherwise there are no tests here to separate from production code, so the folder question hasn't been reached yet.
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 README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
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 39/46 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 46, 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.
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 · 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 — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 8 use(s) across 57,051 production line(s) (~0.1/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock, and, where the code is a reusable library, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a 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).
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.
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
14 of the 644 unreached modules are entry points — the browser loads some as a top-level script and something else executes the rest by path, so no import specifier addresses them and no public entry publishes them. An importing test cannot be written for them as they ship, and two different things are worth doing here — they are not the same thing. To EXERCISE them, a browser or end-to-end suite that loads the page, or a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make them addressable: lift the logic into a module a test can import and leave the entry points thin shims over it, or put their bodies behind a main-guard (`import.meta.url === argv[1]`) and export them. Add tests that import the other 630 — directly or through their public entry.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · 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).
`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
No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
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, X-Frame-Options, X-Content-Type-Options) — 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. 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. 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. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. 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.
Only 297/383 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×39) — 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, …
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 the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — 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 the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — 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 the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — 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.
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. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere. 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. 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. 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. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/Services/Catalog/Core/Catalog.Infrastructure/Data/InitialData.cs:54
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
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. 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.
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 — 21 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.
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.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
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
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
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
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 · ×26
<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).
Banned license: MySql.Data — `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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.EntityFrameworkCore — `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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.Auditing — `Volo.Abp.Auditing` 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.Authorization — `Volo.Abp.Authorization` 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.ExceptionHandling — `Volo.Abp.ExceptionHandling` 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.Http — `Volo.Abp.Http` 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.Security — `Volo.Abp.Security` 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.Uow — `Volo.Abp.Uow` 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.Validation — `Volo.Abp.Validation` 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 match is a SUBSTRING of the id, not an exact comparison — which is how variants like `-only` and `-or-later` are caught, 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.
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.
Dual write (no outbox): CreateProductCommandHandler.Handle src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:66— `CreateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): PublishProductCommandHandler.Handle src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/PublishProductCommand.cs:37— `PublishProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): UpdateProductCommandHandler.Handle src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:67— `UpdateProductCommandHandler.Handle` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
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.
Domain depends on infrastructure: DeletedUnPublishedProductDomainEventHandler src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/DeletedUnPublishedProductDomainEventHandler.cs:15— `DeletedUnPublishedProductDomainEventHandler` (domain layer) references `Marten` — an infrastructure concern (persistence/HTTP/web).
Domain depends on infrastructure: UpsertedProductDomainEventHandler src/Services/Catalog/Core/Catalog.Application/Features/Product/EventHandlers/Domain/UpsertedProductDomainEventHandler.cs:15— `UpsertedProductDomainEventHandler` (domain layer) references `Marten` — an infrastructure concern (persistence/HTTP/web).
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— 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.
DM12 · Ambient inputs in the domain· Domain type reads the wall clock · ×26
Domain type reads the wall clock: BasketCheckoutDomainEventHandler src/Services/Basket/Core/Basket.Application/Features/Basket/EventHandlers/Domain/BasketCheckoutDomainEventHandler.cs:32— `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:21— `BrandEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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:25— `CategoryEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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:42— `CouponEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `Update`, `Approve`, `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: DashboardTotalEntity src/Services/Report/Core/Report.Domain/Entities/DashboardTotalEntity.cs:27— `DashboardTotalEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateCount`, `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:32— `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:38— `DeliveryEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateStatus`, `RaiseError`. 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: InventoryHistoryEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryHistoryEntity.cs:19— `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`.
Domain type reads the wall clock: InventoryItemDeletedDomainEventHandler src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/InventoryItemDeletedDomainEventHandler.cs:34— `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`.
Domain type reads the wall clock: InventoryItemEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryItemEntity.cs:72— `InventoryItemEntity` reads `DateTimeOffset.UtcNow` inside `Update`, `Decrease`, `Reserve`, `Unreserve`. 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: InventoryReservationEntity src/Services/Inventory/Core/Inventory.Domain/Entities/InventoryReservationEntity.cs:69— `InventoryReservationEntity` reads `DateTimeOffset.UtcNow` inside `MarkCommitted`, `Release`, `Expire`. 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: LocationEntity src/Services/Inventory/Core/Inventory.Domain/Entities/LocationEntity.cs:19— `LocationEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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: NotificationEntity src/Services/Notification/Core/Notification.Domain/Entities/NotificationEntity.cs:32— `NotificationEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `MarkAsRead`, `UpdateTargetUrl`. 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: OrderCancelledDomainEventHandler src/Services/Order/Core/Order.Application/Features/Order/EventHandlers/Domain/OrderCancelledDomainEventHandler.cs:32— `OrderCancelledDomainEventHandler` 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: OrderCreatedDomainEventHandler src/Services/Order/Core/Order.Application/Features/Order/EventHandlers/Domain/OrderCreatedDomainEventHandler.cs:34— `OrderCreatedDomainEventHandler` 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: OrderDeliveredDomainEventHandler src/Services/Order/Core/Order.Application/Features/Order/EventHandlers/Domain/OrderDeliveredDomainEventHandler.cs:32— `OrderDeliveredDomainEventHandler` 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: OrderEntity src/Services/Order/Core/Order.Domain/Entities/OrderEntity.cs:86— `OrderEntity` reads `DateTimeOffset.UtcNow` inside `UpdateShippingAddress`, `UpdateCustomerInfo`, `UpdateStatus`, `CancelOrder`. 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: OrderGrowthLineChartEntity src/Services/Report/Core/Report.Domain/Entities/OrderGrowthLineChartEntity.cs:23— `OrderGrowthLineChartEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateValue`. 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: OrderNo src/Services/Order/Core/Order.Domain/ValueObjects/OrderNo.cs:19— `OrderNo` reads `DateTimeOffset.Now` 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: ProductEntity src/Services/Catalog/Core/Catalog.Domain/Entities/ProductEntity.cs:64— `ProductEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `Update`, `Publish`, `Unpublish`. 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: ProductEntity src/Services/Search/Core/Search.Domain/Entities/ProductEntity.cs:36— `ProductEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `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: ReservationExpiredDomainEventHandler src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationExpiredDomainEventHandler.cs:45— `ReservationExpiredDomainEventHandler` 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: StockChangedDomainEventHandler src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/StockChangedDomainEventHandler.cs:34— `StockChangedDomainEventHandler` 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: TemplateEntity src/Services/Notification/Core/Notification.Domain/Entities/TemplateEntity.cs:28— `TemplateEntity` 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: TopProductPieChartEntity src/Services/Report/Core/Report.Domain/Entities/TopProductPieChartEntity.cs:21— `TopProductPieChartEntity` reads `DateTimeOffset.UtcNow` inside `Create`, `UpdateValue`. 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`.
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.
Deprecated: AutoMapper.Extensions.Microsoft.DependencyInjection — 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 — Polly.Extensions.Http 3.0.0 — Legacy — the publisher's replacement is `Microsoft.Extensions.Http.Resilience`; migrate the reference to it.
Deprecated: Elasticsearch.Net — Elasticsearch.Net 7.17.5 — Legacy — the publisher's replacement is `Elastic.Clients.Elasticsearch`; migrate the reference to it.
Deprecated: NEST — NEST 7.17.5 — Legacy — the publisher's replacement is `Elastic.Clients.Elasticsearch`; migrate the reference to it.
DM7 · Repository granularity· Repository for a non-root entity · ×6
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: InventoryItemRepository → InventoryItemEntity src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/InventoryItemRepository.cs:15— `InventoryItemRepository` is a repository over `InventoryItemEntity`, 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 `InventoryItemEntity` through its owning aggregate instead.
Repository for a non-root entity: InventoryReservationRepository → InventoryReservationEntity src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/InventoryReservationRepository.cs:12— `InventoryReservationRepository` is a repository over `InventoryReservationEntity`, 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 `InventoryReservationEntity` 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.
Repository for a non-root entity: OrderRepository → OrderEntity src/Services/Order/Core/Order.Infrastructure/Repositories/OrderRepository.cs:15— `OrderRepository` is a repository over `OrderEntity`, 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 `OrderEntity` through its owning aggregate instead.
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.
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 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (19 lines × 2) src/Services/Search/Core/Search.Application/Dtos/Products/ProductDto.cs:14— src/Services/Search/Core/Search.Application/Dtos/Products/ProductDto.cs:14-32 | src/Services/Search/Core/Search.Application/Dtos/Products/UpsertProductDto.cs:15-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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) src/Shared/Common/Extensions/StringExtension.cs:21— src/Shared/Common/Extensions/StringExtension.cs:21-29 | src/Shared/Common/Extensions/StringExtension.cs:40-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationCommittedDomainEventHandler.cs:32— src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationCommittedDomainEventHandler.cs:32-40 | src/Services/Inventory/Core/Inventory.Application/Features/InventoryReservation/EventHandlers/Domain/ReservationExpiredDomainEventHandler.cs:35-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) 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/Inventory/Worker/Inventory.Worker.Outbox/Factories/DatabaseProviderFactory.cs:16— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Factories/DatabaseProviderFactory.cs:16-24 | src/Services/Order/Worker/Order.Woker.Outbox/Factories/DatabaseProviderFactory.cs:16-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.
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 · ×5
Domain type reads a global random source: InboxMessageEntity src/Services/Order/Core/Order.Domain/Entities/InboxMessageEntity.cs:65— `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.
Domain type reads a global random source: OutboxMessageEntity src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:73— `OutboxMessageEntity` 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.
Domain type reads a global random source: OutboxMessageEntity src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:73— `OutboxMessageEntity` 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.
Domain type reads a global random source: OutboxMessageEntity src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs:65— `OutboxMessageEntity` 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.
Domain type reads a global random source: OutboxMessageEntity src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:73— `OutboxMessageEntity` 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.
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.
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.
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 (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 (31 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:73— src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:73-103 | src/Services/Order/Core/Order.Infrastructure/Services/CatalogGrpcService.cs:73-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.
Duplicated block (31 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:21— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:21-51 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:21-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. 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 (31 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:21— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:21-51 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:21-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. 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 (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 (29 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:57— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:57-85 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/MySqlDatabaseProvider.cs:57-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/MySqlDatabaseProvider.cs:57` 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 × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:21— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:21-49 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:21-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. 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 (29 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:55— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:55-83 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/SqlServerDatabaseProvider.cs:55-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/SqlServerDatabaseProvider.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
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.
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 (18 lines × 2) src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/InventoryItemDeletedDomainEventHandler.cs:35— src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/InventoryItemDeletedDomainEventHandler.cs:35-52 | src/Services/Inventory/Core/Inventory.Application/Features/InventoryItem/EventHandlers/Domain/StockChangedDomainEventHandler.cs:35-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 (18 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs:35— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs:35-52 | src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/AuditableEntityInterceptor.cs:35-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) 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 (17 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:30— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:30-46 | src/Services/Order/Core/Order.Infrastructure/Data/Interceptors/DispatchDomainEventsInterceptor.cs:30-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.
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 (17 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:69— src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:69-85 | src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:111-127 — 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:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:140— src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:140-153 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:173-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 75 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 (14 lines × 2) src/Services/Order/Core/Order.Application/Dtos/ValueObjects/AddressDto.cs:4— src/Services/Order/Core/Order.Application/Dtos/ValueObjects/AddressDto.cs:4-17 | src/Services/Order/Core/Order.Domain/ValueObjects/Address.cs:4-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/Order/Core/Order.Application/Dtos/ValueObjects/AddressDto.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 (14 lines × 2) src/Services/Order/Core/Order.Application/Models/Filters/GetAllOrdersFilter.cs:10— src/Services/Order/Core/Order.Application/Models/Filters/GetAllOrdersFilter.cs:10-23 | src/Services/Order/Core/Order.Application/Models/Filters/GetOrdersFilter.cs:10-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Order/Core/Order.Application/Models/Filters/GetAllOrdersFilter.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 (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 (12 lines × 2) src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/CreateCouponCommand.cs:44— src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/CreateCouponCommand.cs:44-55 | src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/UpdateCouponCommand.cs:41-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Discount/Core/Discount.Application/Features/Coupon/Commands/CreateCouponCommand.cs:44` 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 (12 lines × 2) src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:32— src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:32-43 | src/Services/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:92-103 — 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/Notification/Core/Notification.Infrastructure/Repositories/NotificationRepository.cs:32` 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/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.
Off the main sequence: Common — 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: EventSourcing — EventSourcing: abstractness 0.00, instability 0.02, distance 0.98 — zone of pain — concrete and depended on by 40 project(s), so it's rigid to change.
Off the main sequence: BuildingBlocks — BuildingBlocks: abstractness 0.23, instability 0.02, distance 0.75 — 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.
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 the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
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 the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
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 the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
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.
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.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.
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.
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 (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 (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 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.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 (21 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:52— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:52-72 | src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs:52-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 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:83— src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:83-102 | src/Services/Basket/Core/Basket.Infrastructure/Repositories/OutboxRepository.cs:129-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:83` 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 (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 (16 lines × 4) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:4— src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:4-19 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:4-19 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:4-19 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:8-23 — 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 92 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/Api/Catalog.Api/Models/CreateProductRequest.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 (16 lines × 4) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:17— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:17-32 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17-32 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:17-32 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:17-32 — 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 (15 lines × 4) src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9— src/Services/Basket/Core/Basket.Domain/Entities/OutboxMessageEntity.cs:9-23 | src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:9-23 | src/Services/Inventory/Core/Inventory.Domain/Entities/OutboxMessageEntity.cs:9-23 | src/Services/Order/Core/Order.Domain/Entities/OutboxMessageEntity.cs:9-23 — 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 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.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. 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 (13 lines × 5) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:25— src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:25-37 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:27-39 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:25-37 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:33-45 | src/Services/Catalog/Core/Catalog.Domain/Entities/ProductEntity.cs:36-48 — 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 92 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 5) src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:25— src/Services/Basket/Core/Basket.Infrastructure/DependencyInjection.cs:25-37 | src/Services/Catalog/Core/Catalog.Infrastructure/DependencyInjection.cs:27-39 | src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:34-46 | src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs:28-40 | src/Services/Search/Core/Search.Infrastructure/DependencyInjection.cs:23-35 — 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 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 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.
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 (11 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:156— src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/CreateProductCommand.cs:156-166 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Commands/UpdateProductCommand.cs:189-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 75 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 (8 lines × 2) src/Services/Notification/Api/Notification.Api/DependencyInjection.cs:21— src/Services/Notification/Api/Notification.Api/DependencyInjection.cs:21-28 | src/Services/Report/Api/Report.Api/DependencyInjection.cs:21-28 — before extracting anything, compare `src/Services/Notification/Api/Notification.Api/DependencyInjection.cs` and `src/Services/Report/Api/Report.Api/DependencyInjection.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Notification/Api/Notification.Api/DependencyInjection.cs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (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.Infrastructure/DependencyInjection.cs:25— src/Services/Inventory/Core/Inventory.Infrastructure/DependencyInjection.cs:25-31 | src/Services/Order/Core/Order.Infrastructure/DependencyInjection.cs:24-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Core/Inventory.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 (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 (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 (6 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/DatabaseExtentions.cs:18— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Extensions/DatabaseExtentions.cs:18-23 | src/Services/Order/Core/Order.Infrastructure/Data/Extensions/DatabaseExtentions.cs:15-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.
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 78 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.
Non-idempotent mutation: Commands.CreateLocationCommandHandler.Handle src/Services/Inventory/Core/Inventory.Application/Features/Location/Commands/CreateLocationCommand.cs:38— `Commands.CreateLocationCommandHandler.Handle` mutates persistent state (a database save) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Non-idempotent mutation: Commands.DeleteProductCommandHandler.Handle src/Services/Search/Core/Search.Application/Features/Product/Commands/DeleteProductCommand.cs:18— `Commands.DeleteProductCommandHandler.Handle` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
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.
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.3: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.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 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 literals 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 literals 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.
FarzaaContext.FarzaaContextProvider (cyclomatic 115) src/Apps/App.Store/src/context/FarzaaContext.jsx:14— FarzaaContext.FarzaaContextProvider has cyclomatic complexity 115 (threshold 15). Most of this is not in the body itself: 3 of the 115 points are its own statements and the rest belongs to 38 function literals inside it that branch (lines 244, 211, 167, …). 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.
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 literals 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 literals 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-product.EditProduct (cyclomatic 73) src/Apps/App.Admin/src/pages/product/edit-product.jsx:17— edit-product.EditProduct has cyclomatic complexity 73 (threshold 15). Of this number, 17 points are the body's own statements and 56 belong to 10 function literals 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 (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 literals 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 literals 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 literals inside it that branch (lines 163, 118, 83). 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.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 literals 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 literals inside it that branch (lines 44, 122, 169, …). 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-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 literals 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 literals 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 literals 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 literals 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 literals 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 literals inside it that branch (lines 30, 173, 84, …). 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.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 literals inside it that branch (lines 91, 117, 140, …). 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.
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 literals 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 literals 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.
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.
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 literals 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 literals inside it that branch (lines 80, 45, 51, …). 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.
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 literals 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 ((anonymous), getConsistentRedirectUri, (anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
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 literals 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 literals 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 literals inside it that branch (lines 113, 46, 13, …). 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.
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 literals 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.
FarzaaContext.FarzaaContextProvider (cognitive 147) src/Apps/App.Store/src/context/FarzaaContext.jsx:14— FarzaaContext.FarzaaContextProvider has cognitive complexity 147 (threshold 15). Drivers by points: if/else 78 (92 pts), boolean chains 26, ternaries 17 (22 pts), error handling 5, loops 1, match/switch 1 (nesting depth added 19). Most of this is not in the body itself: 2 of the 147 points are its own statements and the rest belongs to 38 function literals inside it that branch (lines 244, 211, 519, …). 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.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 literals 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 literals 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 literals 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 literals 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.
edit-product.EditProduct (cognitive 68) src/Apps/App.Admin/src/pages/product/edit-product.jsx:17— edit-product.EditProduct has cognitive complexity 68 (threshold 15). Drivers by points: boolean chains 38, if/else 13, ternaries 13, error handling 4. Of this number, 16 points are the body's own statements and 52 belong to 10 function literals 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 (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 literals 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 literals 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 literals inside it that branch (lines 122, 44, 25, …). 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.
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 literals inside it that branch (lines 163, 118, 83). 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-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 literals 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 literals 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 literals inside it that branch (lines 136, 33, 54, …). 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.
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 literals inside it that branch (lines 30, 173, 62, …). 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 (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 literals 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 literals inside it that branch (lines 91, 117, 333, …). 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.
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 literals 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 literals inside it that branch (lines 46, 113, 13, …). 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.
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). Most of this is not in the body itself: 0 of the 22 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 80, 13, 27, …). 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.
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 literals 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 literals 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 ((anonymous), getConsistentRedirectUri, (anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where 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.
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 literals 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). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (translateMenuItems::(anonymous), translateMenuItems::(anonymous)::(anonymous), translateMenuItems::(anonymous)::(anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where 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 ((anonymous), onTokenExpired::(anonymous), onAuthSuccess, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where 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). Most of this is not in the body itself: 0 of the 16 points are its own statements and the rest belongs 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.
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 literals inside it that branch (lines 122, 114, 180, …). 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.
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.
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) src/Services/Basket/Api/Basket.Api/DependencyInjection.cs:67— src/Services/Basket/Api/Basket.Api/DependencyInjection.cs:67-96 | src/Services/Catalog/Api/Catalog.Api/DependencyInjection.cs:64-93 | src/Services/Discount/Api/Discount.Api/DependencyInjection.cs:67-96 | src/Services/Inventory/Api/Inventory.Api/DependencyInjection.cs:63-92 | src/Services/Notification/Api/Notification.Api/DependencyInjection.cs:62-91 | src/Services/Order/Api/Order.Api/DependencyInjection.cs:63-92 | src/Services/Report/Api/Report.Api/DependencyInjection.cs:62-91 | src/Services/Search/Api/Search.Api/DependencyInjection.cs: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 (52 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:78— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Processors/OutboxProcessor.cs:78-129 | src/Services/Order/Worker/Order.Woker.Outbox/Processors/OutboxProcessor.cs:78-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 78 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 (39 lines × 2) src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:18— src/Services/Basket/Core/Basket.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:18-56 | src/Services/Order/Core/Order.Infrastructure/GrpcClients/Extensions/GrpcClientExtension.cs:18-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.
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 80 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 80 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 (33 lines × 2) src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:30— src/Services/Notification/Core/Notification.Infrastructure/DependencyInjection.cs:30-62 | src/Services/Report/Core/Report.Infrastructure/DependencyInjection.cs:24-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 58 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:30` 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 (32 lines × 3) src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakUser.cs:10— src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakUser.cs:10-41 | src/Services/Notification/Core/Notification.Domain/Models/Externals/Keycloaks/KeycloakUser.cs:10-41 | src/Services/Report/Core/Report.Domain/Models/Externals/Keycloaks/KeycloakUser.cs:10-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakUser.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 (32 lines × 2) src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs:53— src/Services/Catalog/Api/Catalog.Api/Endpoints/CreateProduct.cs:53-84 | src/Services/Catalog/Api/Catalog.Api/Endpoints/UpdateProduct.cs:54-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 × 3) src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:41— src/Services/Basket/Core/Basket.Infrastructure/Services/CatalogGrpcService.cs:41-70 | src/Services/Inventory/Core/Inventory.Infrastructure/Services/CatalogGrpcService.cs:44-73 | src/Services/Order/Core/Order.Infrastructure/Services/CatalogGrpcService.cs:41-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.
Duplicated block (30 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:16— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:16-45 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:16-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 75 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:16` 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 × 8) src/Services/Basket/Api/Basket.Api/DependencyInjection.cs:68— src/Services/Basket/Api/Basket.Api/DependencyInjection.cs:68-96 | src/Services/Catalog/Api/Catalog.Api/DependencyInjection.cs:65-93 | src/Services/Discount/Api/Discount.Api/DependencyInjection.cs:68-96 | src/Services/Inventory/Api/Inventory.Api/DependencyInjection.cs:64-92 | src/Services/Notification/Api/Notification.Api/DependencyInjection.cs:63-91 | src/Services/Order/Api/Order.Api/DependencyInjection.cs:64-92 | src/Services/Report/Api/Report.Api/DependencyInjection.cs:63-91 | src/Services/Search/Api/Search.Api/DependencyInjection.cs:74-102 — before extracting anything, compare `src/Services/Basket/Api/Basket.Api/DependencyInjection.cs` and `src/Services/Catalog/Api/Catalog.Api/DependencyInjection.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/Search/Api/Search.Api/DependencyInjection.cs: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, `src/Services/Search/Api/Search.Api/DependencyInjection.cs:72` calls `UseInfrastructure` and `src/Services/Basket/Api/Basket.Api/DependencyInjection.cs: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 (29 lines × 3) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:33— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:33-61 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:33-61 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OutboxMessageConfiguration.cs:33-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 75 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:33` 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 92 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 (27 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:16— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:16-42 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:16-42 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InboxMessageConfiguration.cs:16` 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 (26 lines × 3) src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:46— src/Services/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:46-71 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/BackgroundServices/OutboxBackgroundService.cs:47-72 | src/Services/Order/Worker/Order.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:46-71 — 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 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/Catalog/Worker/Catalog.Woker.Outbox/BackgroundServices/OutboxBackgroundService.cs:46` 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 (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 75 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 (25 lines × 2) src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:57— src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:57-81 | src/Services/Order/Worker/Order.Woker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:57-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Worker/Inventory.Worker.Outbox/Providers/PostgreSqlDatabaseProvider.cs:57` 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 (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 75 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 (23 lines × 5) src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakAccessToken.cs:10— src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakAccessToken.cs:10-32 | src/Services/Inventory/Core/Inventory.Application/Models/Responses/Externals/KeycloakAccessTokenResponse.cs:10-32 | src/Services/Notification/Core/Notification.Domain/Models/Externals/Keycloaks/KeycloakAccessToken.cs:10-32 | src/Services/Order/Core/Order.Application/Models/Responses/KeycloakAccessTokenResponse.cs:10-32 | src/Services/Report/Core/Report.Domain/Models/Externals/Keycloaks/KeycloakAccessToken.cs:10-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/JobOrchestrator/App.Job/Models/Keycloaks/KeycloakAccessToken.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 (23 lines × 4) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:23— src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:23-45 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:25-47 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:23-45 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:31-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 92 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 (23 lines × 3) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:54— src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:54-76 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductByIdQuery.cs:32-54 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductsQuery.cs:55-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. ★ 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 (20 lines × 5) 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 — 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 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 (20 lines × 4) 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 — 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.
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 (17 lines × 5) src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryHistoryConfiguration.cs:25— src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryHistoryConfiguration.cs:25-41 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryItemConfiguration.cs:29-45 | src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryReservationConfiguration.cs:33-49 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OrderEntityConfiguration.cs:35-51 | src/Services/Order/Core/Order.Infrastructure/Data/Configurations/OrderItemEntityConfiguration.cs:30-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Services/Inventory/Core/Inventory.Infrastructure/Data/Configurations/InventoryHistoryConfiguration.cs:25` 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<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–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 (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 (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 (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 (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 (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 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:27— src/Services/Catalog/Api/Catalog.Api/Models/CreateProductRequest.cs:27-37 | src/Services/Catalog/Api/Catalog.Api/Models/UpdateProductRequest.cs:29-39 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/CreateProductDto.cs:27-37 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/ProductInfoDto.cs:34-44 | src/Services/Catalog/Core/Catalog.Application/Dtos/Products/UpdateProductDto.cs:35-45 — 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 92 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 (11 lines × 3) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:24— src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllAvailableProductsQuery.cs:24-34 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetAllProductsQuery.cs:24-34 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:28-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 80 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 (10 lines × 2) src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:37— src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetProductsQuery.cs:37-46 | src/Services/Catalog/Core/Catalog.Application/Features/Product/Queries/GetPublishProductsQuery.cs:33-42 — 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/GetProductsQuery.cs:37` 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 (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 (21 lines × 5) src/Services/Catalog/Api/Catalog.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:20— src/Services/Catalog/Api/Catalog.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:20-40 | src/Services/Discount/Api/Discount.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:20-40 | src/Services/Inventory/Api/Inventory.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:20-40 | src/Services/Order/Api/Order.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:20-40 | src/Services/Report/Api/Report.Grpc/Interceptors/ApiKeyValidationInterceptor.cs:20-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.
Duplicated block (84 lines × 2) src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/Repository.cs:25— src/Services/Inventory/Core/Inventory.Infrastructure/Repositories/Repository.cs:25-108 | src/Services/Order/Core/Order.Infrastructure/Repositories/Repository.cs:25-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 (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) src/Services/Basket/Api/Basket.Api/DependencyInjection.cs:23— src/Services/Basket/Api/Basket.Api/DependencyInjection.cs:23-64 | src/Services/Discount/Api/Discount.Api/DependencyInjection.cs:23-64 | src/Services/Inventory/Api/Inventory.Api/DependencyInjection.cs:21-60 | src/Services/Order/Api/Order.Api/DependencyInjection.cs:21-60 | src/Services/Search/Api/Search.Api/DependencyInjection.cs:25-68 — before extracting anything, compare `src/Services/Basket/Api/Basket.Api/DependencyInjection.cs` and `src/Services/Discount/Api/Discount.Api/DependencyInjection.cs` 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, `src/Services/Search/Api/Search.Api/DependencyInjection.cs:72` calls `UseInfrastructure` and `src/Services/Basket/Api/Basket.Api/DependencyInjection.cs: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 (7 lines × 4) src/Services/Basket/Worker/Basket.Worker.Outbox/DependencyInjection.cs:19— src/Services/Basket/Worker/Basket.Worker.Outbox/DependencyInjection.cs:19-25 | src/Services/Catalog/Worker/Catalog.Woker.Outbox/DependencyInjection.cs:19-25 | src/Services/Inventory/Worker/Inventory.Worker.Outbox/DependencyInjection.cs:19-25 | src/Services/Order/Worker/Order.Woker.Outbox/DependencyInjection.cs:19-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. 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 (10 lines × 5) src/Services/Catalog/Worker/Catalog.Worker.Consumer/BackgroundServices/CatalogBackgroudService.cs:8— src/Services/Catalog/Worker/Catalog.Worker.Consumer/BackgroundServices/CatalogBackgroudService.cs:8-17 | src/Services/Inventory/Worker/Inventory.Worker.Consumer/BackgroundServices/InventoryBackgroudService.cs:8-17 | src/Services/Notification/Worker/Notification.Worker.Consumer/BackgroundServices/NotificationBackgroundService.cs:8-17 | src/Services/Order/Worker/Order.Worker.Consumer/BackgroundServices/OrderBackgroudService.cs:8-17 | src/Services/Search/Worker/Search.Worker.Consumer/BackgroundServices/SearchBackgroudService.cs:8-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.
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.
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.
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).
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.
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.
Swallowed exception (caught, then discarded) src/Services/Catalog/Core/Catalog.Infrastructure/Data/InitialData.cs:54— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Minor — 159 finding(s)
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).
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.
DM8 · Value-object opportunities· Primitive data clump · ×4
Primitive data clump: [content, eventtype, id] src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:35— The parameters [content, eventtype, id] travel together across 6 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
Primitive data clump: [attemptcount, lasterrormessage, maxattempts] src/Services/Catalog/Core/Catalog.Domain/Entities/OutboxMessageEntity.cs:65— The parameters [attemptcount, lasterrormessage, maxattempts] travel together across 5 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
Primitive data clump: [addressline, city, country, postalcode, stateorprovince, subdivision] src/Services/Order/Core/Order.Domain/ValueObjects/Address.cs:37— The parameters [addressline, city, country, postalcode, stateorprovince, subdivision] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
Primitive data clump: [email, id, name, phonenumber] src/Services/Order/Core/Order.Domain/ValueObjects/Customer.cs:27— The parameters [email, id, name, phonenumber] travel together across 3 signatures and were confirmed as a coherent concept by the model — that's a missing value object. Extracting them into one type (e.g. `Address`, `Money`, `Coordinate`) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules.
redundant comment src/ApiGateway/YarpApiGateway/Program.cs:13— "Add services to the container." —
redundant comment src/JobOrchestrator/App.Job/Quartz/JobRegistrationExtensions.cs:51— "Register job to scheduler" —
redundant comment src/Services/Basket/Api/Basket.Api/DependencyInjection.cs:28— "HealthChecks" — delete - duplicate of HealthChecks comment above the block
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.
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 — 6 file(s) are concentrated to one author — the ambient state with 2 active author(s), not 6 separate risks. The signal becomes meaningful as ownership spreads; no per-file action implied now.
Documentation: no installation or build instructions README.md— The README does not provide any build or setup steps, such as how to install dependencies or run the project. Add a short Install/Build section covering NuGet package restore and dotnet CLI commands.
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/`.
D21 · Naming Consistency· The class name 'DatabaseExtentions' contains a spelling error ('Extentions' instead of 'Extensions'). This misspelling is consistently applied to the type and its members, but it represents a deviation from the standard English spelling convention for this common technical term. · ×1
The class name 'DatabaseExtentions' contains a spelling error ('Extentions' instead of 'Extensions'). This misspelling is consistently applied to the type and its members, but it represents a deviation from the standard English spelling convention for this common technical term. — Rename the type and namespace references to 'DatabaseExtensions' to correct the spelling. (symbols: Type: public Report.Infrastructure.Data.Extensions.DatabaseExtentions, Method: public Report.Infrastructure.Data.Extensions.DatabaseExtentions.InitialiseDatabaseAsync(Microsoft.AspNetCore.Builder.WebApplication), Method: private Report.Infrastructure.Data.Extensions.DatabaseExtentions.SeedDashboardTotalAsync(MongoDB.Driver.IMongoDatabase, string))
D21 · Naming Consistency· The word 'Response' is misspelled as 'Reponse' in two different locations · ×1
The word 'Response' is misspelled as 'Reponse' in two different locations: 'ProductReponse' and 'ApiUpdatedResponse'. This indicates a systematic typo in the codebase's naming for response models. — Rename 'ProductReponse' to 'ProductResponse' and 'ApiUpdatedResponse' to 'ApiResponse' (or 'ApiUpdatedResponse' if the prefix is required) to correct the spelling. (symbols: Property: public Order.Application.Models.Responses.Externals.ProductReponse.Name, Type: public Common.Models.Reponses.ApiUpdatedResponse<T>)
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 20 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/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, src/Services/Order/Worker/Order.Worker.Consumer/EventHandlers/Integrations/ReservationExpiredIntegrationEventHandler.cs (and 12 more) (21 orphaned of 117 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo 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 [Canceled, Delivered, Refunded] decided in 2 places · ×1
Rule about [Canceled, Delivered, Refunded] decided in 2 places — Order.Domain.Enums.OrderStatus's [Canceled, Delivered, Refunded] are judged in Order.Application.Features.Order.Commands.UpdateOrderCommandHandler, Order.Application.Features.Order.Commands.UpdateOrderStatusCommandHandler — 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.
No tests/ separation — No test surface was found — this check walked the tree for authored source in the languages it models (`.cs`, `.vb`, `.fs`, `.java`, `.kt`, `.scala`, `.py`, `.php`, `.rb`, `.ex`, `.exs`, `.go`, `.erl`, `.hrl`, `.swift`, `.dart`, `.rs`, `.ts`, `.tsx`, `.mts`, `.cts`) and found none of it test-shaped. ★ `.js`, `.jsx`, `.mjs` and `.cjs` are NOT in that walk, so a Jest or Mocha suite written in plain JavaScript is invisible to it and this row is then wrong. If that is your case, say so rather than moving anything. Otherwise there are no tests here to separate from production code, so the folder question hasn't been reached yet.
Logging is not universal — Only 39/46 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 46, 15 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) 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.
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.
No security response headers detected — No Content-Security-Policy / X-Frame-Options / X-Content-Type-Options configuration found — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
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.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 297/383 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.
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.
dotnet list progcoder-shop-microservices.sln package --vulnerable --include-transitive --format json
0
artifacts/raw/dotnet-vulnerable.json
Run 01a0c4d4-0480-7d5b-acaf-29cfda5e504c · 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: 536 · Warnings: 666 · Recommendations: 159 · Info: 345 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-09-2026 @ 16:37 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.