Public report of entelect-incubator/Project-Templates, published 22 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 22 October 2026, 04:51 UTC · Survey ID cd_cf0c4ddb30e04df485a9dc1aa4309964
entelect-incubator/Project-Templates
Measured 22 October 2026, 04:43 UTC, at code version cb2c497
Code coverage is not measured: .NET and JavaScript/TypeScript suite (CouldNotMeasureEnvironment, CouldNotMeasureRepoBuildError).
Bus factor is not measured: One contributor carries this repository.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 6 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A small codebase: 5,164 lines of product code in 48 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 23
Findings by how serious they are
124 critical461 serious473 minor
6 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 04:43 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
93of 101 dimensions measured by tools. The other 8 are advisory notes from an AI model, which explain the code but don't count towards the score.
679of 1058 findings point to an exact file and line, so you can open each one in the code. The other 379 concern the repository as a whole, such as missing documentation.
101dimensions across 7 lenses, read from 5,164 lines of product code in 48 projects.
entelect-incubator/Project-Templates scores 40 out of 100, which would normally be rated Adequate, but it is rated Weak because its weakest group of dimensions, Dependencies, is rated Critical. The standard never rates a score more than one step above its weakest group, so a high average can't hide a weak area. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 23 and is rated Weak. Its Dependency Hygiene dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 3 Leaked secret finding(s) in Secret Scanning and to resolve the 2 Vulnerable finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 40 to about 55.
124 findings are critical: 82 in Dependency Vulnerabilities, 21 in Static Analysis (SAST), eight in IaC & Container Security, five in Forms & labels, three in Secret Scanning, two in Dependency Hygiene, two in Secrets (history) and one in Test Reliability.
Watchdog couldn't measure Navigability, IL Efficiency and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 5,164 lines, which would take an estimated 0.1 person-years, around €6,700, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 23 to 70, the lowest score rated Strong, the score would rise from 40 to about 55.
Code composition: what the lines of code are
Supporting code 17%Tests 83%
New since the last survey: 199 findings
These 199 critical or serious findings weren't in the previous survey, on 7 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Large Files · frontend/Angular/src/app/core/observability/opentelemetry.service.ts: 489 lines of code frontend/Angular/src/app/core/observability/opentelemetry.service.ts
Large Files · frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts: 428 lines of code frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts
Cancellation propagation · Async method without CancellationToken: HandleValidationExceptionAsync backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs
Cancellation propagation · Async method without CancellationToken: HandleOperationCanceledExceptionAsync backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 34 findings
These 34 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Supply-chain Provenance & Signing REDACTED
Test Coverage · This test file cannot be loaded backend/Node/tests/integration/pizzas.integration.test.ts
Test Coverage · This test file cannot be loaded backend/Node/tests/unit/createPizza.test.ts
Tooling · The declared test suite includes a file that cannot be loaded backend/Node/tests/integration/pizzas.integration.test.ts
Slice cohesion · Cross-slice coupling: pizzas → order frontend/React/src/features/pizzas/types/index.ts
Slice cohesion · Cross-slice coupling: pizzas → order frontend/React/src/features/pizzas/types/index.ts
Async & latency hygiene · Awaits without ConfigureAwait(false)
Rebuild cost: about €6,700 · Estimate
Cost to rebuild
€2,200 to €11,000, for 37 to 117 hours of work, about 0.1 person-years for one engineer
Difficulty of the problem
High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 40. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Small: 5,164 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 15 points · Low effort · Secret Scanning
2
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €6,700 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 23 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 3 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 15 points for low effort, because it clears the 3 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
265 modules, with 274 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 225 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Common.V1.Orders uses Common.V1.Orders.Models, so a change to Common.V1.Orders.Models can break Common.V1.Orders, while a change to Common.V1.Orders can't break Common.V1.Orders.Models.
Position
Below the diagonal: Common.V1.Orders uses a module listed above it, which is the healthy direction.
Common.V1.Pizzas.Models uses Utilities.Models, so a change to Utilities.Models can break Common.V1.Pizzas.Models, while a change to Common.V1.Pizzas.Models can't break Utilities.Models.
Position
Below the diagonal: Common.V1.Pizzas.Models uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Database.Entities uses Core.Orders.V1.Models, so a change to Core.Orders.V1.Models can break Core.Orders.V1.Database.Entities, while a change to Core.Orders.V1.Database.Entities can't break Core.Orders.V1.Models.
Position
Below the diagonal: Core.Orders.V1.Database.Entities uses a module listed above it, which is the healthy direction.
Features uses Features.Pizzas.V1.Entities, so a change to Features.Pizzas.V1.Entities can break Features, while a change to Features can't break Features.Pizzas.V1.Entities.
Position
Below the diagonal: Features uses a module listed above it, which is the healthy direction.
Infrastructure uses Domain.V1.Pizzas, so a change to Domain.V1.Pizzas can break Infrastructure, while a change to Infrastructure can't break Domain.V1.Pizzas.
Position
Below the diagonal: Infrastructure uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.Angular.src.app.features.order.types.order_interface uses a type in clients.generated.react.src.api.generated.
frontend.Angular.src.app.features.order.types.order_interface uses clients.generated.react.src.api.generated, so a change to clients.generated.react.src.api.generated can break frontend.Angular.src.app.features.order.types.order_interface, while a change to frontend.Angular.src.app.features.order.types.order_interface can't break clients.generated.react.src.api.generated.
Position
Below the diagonal: frontend.Angular.src.app.features.order.types.order_interface uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in frontend.Angular.src.app.generated.api.api.pizza_serviceInterface uses a type in clients.generated.react.src.api.generated.
frontend.Angular.src.app.generated.api.api.pizza_serviceInterface uses clients.generated.react.src.api.generated, so a change to clients.generated.react.src.api.generated can break frontend.Angular.src.app.generated.api.api.pizza_serviceInterface, while a change to frontend.Angular.src.app.generated.api.api.pizza_serviceInterface can't break clients.generated.react.src.api.generated.
Position
Below the diagonal: frontend.Angular.src.app.generated.api.api.pizza_serviceInterface uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.Angular.src.app.generated.api.api.pizza_serviceInterface uses a type in frontend.Angular.src.app.generated.api.configuration.
frontend.Angular.src.app.generated.api.api.pizza_serviceInterface uses frontend.Angular.src.app.generated.api.configuration, so a change to frontend.Angular.src.app.generated.api.configuration can break frontend.Angular.src.app.generated.api.api.pizza_serviceInterface, while a change to frontend.Angular.src.app.generated.api.api.pizza_serviceInterface can't break frontend.Angular.src.app.generated.api.configuration.
Position
Below the diagonal: frontend.Angular.src.app.generated.api.api.pizza_serviceInterface uses a module listed above it, which is the healthy direction.
Application.Orders.V1.Commands uses Utilities.CQRS, so a change to Utilities.CQRS can break Application.Orders.V1.Commands, while a change to Application.Orders.V1.Commands can't break Utilities.CQRS.
Position
Below the diagonal: Application.Orders.V1.Commands uses a module listed above it, which is the healthy direction.
Application.Orders.V1.Commands uses Utilities.Results, so a change to Utilities.Results can break Application.Orders.V1.Commands, while a change to Application.Orders.V1.Commands can't break Utilities.Results.
Position
Below the diagonal: Application.Orders.V1.Commands uses a module listed above it, which is the healthy direction.
Application.Orders.V1.Commands uses Infrastructure, so a change to Infrastructure can break Application.Orders.V1.Commands, while a change to Application.Orders.V1.Commands can't break Infrastructure.
Position
Below the diagonal: Application.Orders.V1.Commands uses a module listed above it, which is the healthy direction.
Application.Orders.V1.Queries uses Utilities.CQRS, so a change to Utilities.CQRS can break Application.Orders.V1.Queries, while a change to Application.Orders.V1.Queries can't break Utilities.CQRS.
Position
Below the diagonal: Application.Orders.V1.Queries uses a module listed above it, which is the healthy direction.
Application.Orders.V1.Queries uses Utilities.Results, so a change to Utilities.Results can break Application.Orders.V1.Queries, while a change to Application.Orders.V1.Queries can't break Utilities.Results.
Position
Below the diagonal: Application.Orders.V1.Queries uses a module listed above it, which is the healthy direction.
Application.Orders.V1.Queries uses Infrastructure, so a change to Infrastructure can break Application.Orders.V1.Queries, while a change to Application.Orders.V1.Queries can't break Infrastructure.
Position
Below the diagonal: Application.Orders.V1.Queries uses a module listed above it, which is the healthy direction.
Application.Pizzas.V1.Commands uses Utilities.CQRS, so a change to Utilities.CQRS can break Application.Pizzas.V1.Commands, while a change to Application.Pizzas.V1.Commands can't break Utilities.CQRS.
Position
Below the diagonal: Application.Pizzas.V1.Commands uses a module listed above it, which is the healthy direction.
Application.Pizzas.V1.Commands uses Utilities.Results, so a change to Utilities.Results can break Application.Pizzas.V1.Commands, while a change to Application.Pizzas.V1.Commands can't break Utilities.Results.
Position
Below the diagonal: Application.Pizzas.V1.Commands uses a module listed above it, which is the healthy direction.
Application.Pizzas.V1.Commands uses Infrastructure, so a change to Infrastructure can break Application.Pizzas.V1.Commands, while a change to Application.Pizzas.V1.Commands can't break Infrastructure.
Position
Below the diagonal: Application.Pizzas.V1.Commands uses a module listed above it, which is the healthy direction.
Application.Pizzas.V1.Queries uses Utilities.CQRS, so a change to Utilities.CQRS can break Application.Pizzas.V1.Queries, while a change to Application.Pizzas.V1.Queries can't break Utilities.CQRS.
Position
Below the diagonal: Application.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Application.Pizzas.V1.Queries uses Utilities.Models, so a change to Utilities.Models can break Application.Pizzas.V1.Queries, while a change to Application.Pizzas.V1.Queries can't break Utilities.Models.
Position
Below the diagonal: Application.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Application.Pizzas.V1.Queries uses Utilities.Results, so a change to Utilities.Results can break Application.Pizzas.V1.Queries, while a change to Application.Pizzas.V1.Queries can't break Utilities.Results.
Position
Below the diagonal: Application.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Application.Pizzas.V1.Queries uses Infrastructure, so a change to Infrastructure can break Application.Pizzas.V1.Queries, while a change to Application.Pizzas.V1.Queries can't break Infrastructure.
Position
Below the diagonal: Application.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Common.V1.Pizzas uses Common.V1.Pizzas.Models, so a change to Common.V1.Pizzas.Models can break Common.V1.Pizzas, while a change to Common.V1.Pizzas can't break Common.V1.Pizzas.Models.
Position
Below the diagonal: Common.V1.Pizzas uses a module listed above it, which is the healthy direction.
Core uses Core.Pizzas.V1.Database.Entities, so a change to Core.Pizzas.V1.Database.Entities can break Core, while a change to Core can't break Core.Pizzas.V1.Database.Entities.
Position
Below the diagonal: Core uses a module listed above it, which is the healthy direction.
Core uses Core.Orders.V1.Database.Entities, so a change to Core.Orders.V1.Database.Entities can break Core, while a change to Core can't break Core.Orders.V1.Database.Entities.
Position
Below the diagonal: Core uses a module listed above it, which is the healthy direction.
DataAccess.Contracts.V1 uses Common.V1.Orders.Models, so a change to Common.V1.Orders.Models can break DataAccess.Contracts.V1, while a change to DataAccess.Contracts.V1 can't break Common.V1.Orders.Models.
Position
Below the diagonal: DataAccess.Contracts.V1 uses a module listed above it, which is the healthy direction.
DataAccess.Contracts.V1 uses Utilities.Results, so a change to Utilities.Results can break DataAccess.Contracts.V1, while a change to DataAccess.Contracts.V1 can't break Utilities.Results.
Position
Below the diagonal: DataAccess.Contracts.V1 uses a module listed above it, which is the healthy direction.
DataAccess.Contracts.V1 uses Common.V1.Pizzas.Models, so a change to Common.V1.Pizzas.Models can break DataAccess.Contracts.V1, while a change to DataAccess.Contracts.V1 can't break Common.V1.Pizzas.Models.
Position
Below the diagonal: DataAccess.Contracts.V1 uses a module listed above it, which is the healthy direction.
Features.Pizzas.V1.Queries uses Utilities.CQRS, so a change to Utilities.CQRS can break Features.Pizzas.V1.Queries, while a change to Features.Pizzas.V1.Queries can't break Utilities.CQRS.
Position
Below the diagonal: Features.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Features.Pizzas.V1.Queries uses Utilities.Models, so a change to Utilities.Models can break Features.Pizzas.V1.Queries, while a change to Features.Pizzas.V1.Queries can't break Utilities.Models.
Position
Below the diagonal: Features.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Features.Pizzas.V1.Queries uses Utilities.Results, so a change to Utilities.Results can break Features.Pizzas.V1.Queries, while a change to Features.Pizzas.V1.Queries can't break Utilities.Results.
Position
Below the diagonal: Features.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Features.Pizzas.V1.Queries uses Features, so a change to Features can break Features.Pizzas.V1.Queries, while a change to Features.Pizzas.V1.Queries can't break Features.
Position
Below the diagonal: Features.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
frontend.Angular.src.app.generated.api.api.pizza_service uses clients.generated.react.src.api.generated, so a change to clients.generated.react.src.api.generated can break frontend.Angular.src.app.generated.api.api.pizza_service, while a change to frontend.Angular.src.app.generated.api.api.pizza_service can't break clients.generated.react.src.api.generated.
Position
Below the diagonal: frontend.Angular.src.app.generated.api.api.pizza_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.Angular.src.app.generated.api.api.pizza_service uses a type in frontend.Angular.src.app.generated.api.configuration.
frontend.Angular.src.app.generated.api.api.pizza_service uses frontend.Angular.src.app.generated.api.configuration, so a change to frontend.Angular.src.app.generated.api.configuration can break frontend.Angular.src.app.generated.api.api.pizza_service, while a change to frontend.Angular.src.app.generated.api.api.pizza_service can't break frontend.Angular.src.app.generated.api.configuration.
Position
Below the diagonal: frontend.Angular.src.app.generated.api.api.pizza_service uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in frontend.Angular.src.app.generated.api.api.pizza_service uses a type in frontend.Angular.src.app.generated.api.api.pizza_serviceInterface.
frontend.Angular.src.app.generated.api.api.pizza_service uses frontend.Angular.src.app.generated.api.api.pizza_serviceInterface, so a change to frontend.Angular.src.app.generated.api.api.pizza_serviceInterface can break frontend.Angular.src.app.generated.api.api.pizza_service, while a change to frontend.Angular.src.app.generated.api.api.pizza_service can't break frontend.Angular.src.app.generated.api.api.pizza_serviceInterface.
Position
Below the diagonal: frontend.Angular.src.app.generated.api.api.pizza_service uses a module listed above it, which is the healthy direction.
Api.Controllers.V1 uses Utilities.Results, so a change to Utilities.Results can break Api.Controllers.V1, while a change to Api.Controllers.V1 can't break Utilities.Results.
Position
Below the diagonal: Api.Controllers.V1 uses a module listed above it, which is the healthy direction.
Api.Controllers.V1 uses Application.Orders.V1.Commands, so a change to Application.Orders.V1.Commands can break Api.Controllers.V1, while a change to Api.Controllers.V1 can't break Application.Orders.V1.Commands.
Position
Below the diagonal: Api.Controllers.V1 uses a module listed above it, which is the healthy direction.
Api.Controllers.V1 uses Application.Pizzas.V1.Commands, so a change to Application.Pizzas.V1.Commands can break Api.Controllers.V1, while a change to Api.Controllers.V1 can't break Application.Pizzas.V1.Commands.
Position
Below the diagonal: Api.Controllers.V1 uses a module listed above it, which is the healthy direction.
Api.Controllers.V1 uses Application.Pizzas.V1.Queries, so a change to Application.Pizzas.V1.Queries can break Api.Controllers.V1, while a change to Api.Controllers.V1 can't break Application.Pizzas.V1.Queries.
Position
Below the diagonal: Api.Controllers.V1 uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Commands uses Core.Orders.V1.Models, so a change to Core.Orders.V1.Models can break Core.Orders.V1.Commands, while a change to Core.Orders.V1.Commands can't break Core.Orders.V1.Models.
Position
Below the diagonal: Core.Orders.V1.Commands uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Commands uses Utilities.CQRS, so a change to Utilities.CQRS can break Core.Orders.V1.Commands, while a change to Core.Orders.V1.Commands can't break Utilities.CQRS.
Position
Below the diagonal: Core.Orders.V1.Commands uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Commands uses Utilities.Results, so a change to Utilities.Results can break Core.Orders.V1.Commands, while a change to Core.Orders.V1.Commands can't break Utilities.Results.
Position
Below the diagonal: Core.Orders.V1.Commands uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Queries uses Core.Orders.V1.Models, so a change to Core.Orders.V1.Models can break Core.Orders.V1.Queries, while a change to Core.Orders.V1.Queries can't break Core.Orders.V1.Models.
Position
Below the diagonal: Core.Orders.V1.Queries uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Queries uses Utilities.CQRS, so a change to Utilities.CQRS can break Core.Orders.V1.Queries, while a change to Core.Orders.V1.Queries can't break Utilities.CQRS.
Position
Below the diagonal: Core.Orders.V1.Queries uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Queries uses Utilities.Models, so a change to Utilities.Models can break Core.Orders.V1.Queries, while a change to Core.Orders.V1.Queries can't break Utilities.Models.
Position
Below the diagonal: Core.Orders.V1.Queries uses a module listed above it, which is the healthy direction.
Core.Orders.V1.Queries uses Utilities.Results, so a change to Utilities.Results can break Core.Orders.V1.Queries, while a change to Core.Orders.V1.Queries can't break Utilities.Results.
Position
Below the diagonal: Core.Orders.V1.Queries uses a module listed above it, which is the healthy direction.
Core.Pizzas.V1.Commands uses Utilities.CQRS, so a change to Utilities.CQRS can break Core.Pizzas.V1.Commands, while a change to Core.Pizzas.V1.Commands can't break Utilities.CQRS.
Position
Below the diagonal: Core.Pizzas.V1.Commands uses a module listed above it, which is the healthy direction.
Core.Pizzas.V1.Commands uses Utilities.Results, so a change to Utilities.Results can break Core.Pizzas.V1.Commands, while a change to Core.Pizzas.V1.Commands can't break Utilities.Results.
Position
Below the diagonal: Core.Pizzas.V1.Commands uses a module listed above it, which is the healthy direction.
Core.Pizzas.V1.Queries uses Utilities.CQRS, so a change to Utilities.CQRS can break Core.Pizzas.V1.Queries, while a change to Core.Pizzas.V1.Queries can't break Utilities.CQRS.
Position
Below the diagonal: Core.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Core.Pizzas.V1.Queries uses Utilities.Models, so a change to Utilities.Models can break Core.Pizzas.V1.Queries, while a change to Core.Pizzas.V1.Queries can't break Utilities.Models.
Position
Below the diagonal: Core.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Core.Pizzas.V1.Queries uses Utilities.Results, so a change to Utilities.Results can break Core.Pizzas.V1.Queries, while a change to Core.Pizzas.V1.Queries can't break Utilities.Results.
Position
Below the diagonal: Core.Pizzas.V1.Queries uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Commands uses Common.V1.Orders.Models, so a change to Common.V1.Orders.Models can break Core.V1.Orders.Commands, while a change to Core.V1.Orders.Commands can't break Common.V1.Orders.Models.
Position
Below the diagonal: Core.V1.Orders.Commands uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Commands uses Utilities.CQRS, so a change to Utilities.CQRS can break Core.V1.Orders.Commands, while a change to Core.V1.Orders.Commands can't break Utilities.CQRS.
Position
Below the diagonal: Core.V1.Orders.Commands uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Commands uses Utilities.Results, so a change to Utilities.Results can break Core.V1.Orders.Commands, while a change to Core.V1.Orders.Commands can't break Utilities.Results.
Position
Below the diagonal: Core.V1.Orders.Commands uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Commands uses DataAccess.Contracts.V1, so a change to DataAccess.Contracts.V1 can break Core.V1.Orders.Commands, while a change to Core.V1.Orders.Commands can't break DataAccess.Contracts.V1.
Position
Below the diagonal: Core.V1.Orders.Commands uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Queries uses Common.V1.Orders.Models, so a change to Common.V1.Orders.Models can break Core.V1.Orders.Queries, while a change to Core.V1.Orders.Queries can't break Common.V1.Orders.Models.
Position
Below the diagonal: Core.V1.Orders.Queries uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Queries uses Utilities.CQRS, so a change to Utilities.CQRS can break Core.V1.Orders.Queries, while a change to Core.V1.Orders.Queries can't break Utilities.CQRS.
Position
Below the diagonal: Core.V1.Orders.Queries uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Queries uses Utilities.Results, so a change to Utilities.Results can break Core.V1.Orders.Queries, while a change to Core.V1.Orders.Queries can't break Utilities.Results.
Position
Below the diagonal: Core.V1.Orders.Queries uses a module listed above it, which is the healthy direction.
Core.V1.Orders.Queries uses DataAccess.Contracts.V1, so a change to DataAccess.Contracts.V1 can break Core.V1.Orders.Queries, while a change to Core.V1.Orders.Queries can't break DataAccess.Contracts.V1.
Position
Below the diagonal: Core.V1.Orders.Queries uses a module listed above it, which is the healthy direction.
DataAccess.V1.Orders uses Common.V1.Orders.Models, so a change to Common.V1.Orders.Models can break DataAccess.V1.Orders, while a change to DataAccess.V1.Orders can't break Common.V1.Orders.Models.
Position
Below the diagonal: DataAccess.V1.Orders uses a module listed above it, which is the healthy direction.
DataAccess.V1.Orders uses Utilities.Results, so a change to Utilities.Results can break DataAccess.V1.Orders, while a change to DataAccess.V1.Orders can't break Utilities.Results.
Position
Below the diagonal: DataAccess.V1.Orders uses a module listed above it, which is the healthy direction.
DataAccess.V1.Orders uses Common.V1.Orders, so a change to Common.V1.Orders can break DataAccess.V1.Orders, while a change to DataAccess.V1.Orders can't break Common.V1.Orders.
Position
Below the diagonal: DataAccess.V1.Orders uses a module listed above it, which is the healthy direction.
DataAccess.V1.Orders uses DataAccess.Contracts.V1, so a change to DataAccess.Contracts.V1 can break DataAccess.V1.Orders, while a change to DataAccess.V1.Orders can't break DataAccess.Contracts.V1.
Position
Below the diagonal: DataAccess.V1.Orders uses a module listed above it, which is the healthy direction.
DataAccess.V1.Pizzas uses Utilities.Results, so a change to Utilities.Results can break DataAccess.V1.Pizzas, while a change to DataAccess.V1.Pizzas can't break Utilities.Results.
Position
Below the diagonal: DataAccess.V1.Pizzas uses a module listed above it, which is the healthy direction.
DataAccess.V1.Pizzas uses Common.V1.Pizzas.Models, so a change to Common.V1.Pizzas.Models can break DataAccess.V1.Pizzas, while a change to DataAccess.V1.Pizzas can't break Common.V1.Pizzas.Models.
Position
Below the diagonal: DataAccess.V1.Pizzas uses a module listed above it, which is the healthy direction.
DataAccess.V1.Pizzas uses Common.V1.Pizzas, so a change to Common.V1.Pizzas can break DataAccess.V1.Pizzas, while a change to DataAccess.V1.Pizzas can't break Common.V1.Pizzas.
Position
Below the diagonal: DataAccess.V1.Pizzas uses a module listed above it, which is the healthy direction.
DataAccess.V1.Pizzas uses DataAccess.Contracts.V1, so a change to DataAccess.Contracts.V1 can break DataAccess.V1.Pizzas, while a change to DataAccess.V1.Pizzas can't break DataAccess.Contracts.V1.
Position
Below the diagonal: DataAccess.V1.Pizzas uses a module listed above it, which is the healthy direction.
Api.Endpoints.V1.Orders uses Utilities.CQRS, so a change to Utilities.CQRS can break Api.Endpoints.V1.Orders, while a change to Api.Endpoints.V1.Orders can't break Utilities.CQRS.
Position
Below the diagonal: Api.Endpoints.V1.Orders uses a module listed above it, which is the healthy direction.
Api.Endpoints.V1.Orders uses Core.Orders.V1.Commands, so a change to Core.Orders.V1.Commands can break Api.Endpoints.V1.Orders, while a change to Api.Endpoints.V1.Orders can't break Core.Orders.V1.Commands.
Position
Below the diagonal: Api.Endpoints.V1.Orders uses a module listed above it, which is the healthy direction.
Api.Endpoints.V1.Orders uses Core.Orders.V1.Queries, so a change to Core.Orders.V1.Queries can break Api.Endpoints.V1.Orders, while a change to Api.Endpoints.V1.Orders can't break Core.Orders.V1.Queries.
Position
Below the diagonal: Api.Endpoints.V1.Orders uses a module listed above it, which is the healthy direction.
Api.Endpoints.V1.Pizzas uses Utilities.CQRS, so a change to Utilities.CQRS can break Api.Endpoints.V1.Pizzas, while a change to Api.Endpoints.V1.Pizzas can't break Utilities.CQRS.
Position
Below the diagonal: Api.Endpoints.V1.Pizzas uses a module listed above it, which is the healthy direction.
Api.Endpoints.V1.Pizzas uses Core.Pizzas.V1.Commands, so a change to Core.Pizzas.V1.Commands can break Api.Endpoints.V1.Pizzas, while a change to Api.Endpoints.V1.Pizzas can't break Core.Pizzas.V1.Commands.
Position
Below the diagonal: Api.Endpoints.V1.Pizzas uses a module listed above it, which is the healthy direction.
Api.Endpoints.V1.Pizzas uses Core.Pizzas.V1.Queries, so a change to Core.Pizzas.V1.Queries can break Api.Endpoints.V1.Pizzas, while a change to Api.Endpoints.V1.Pizzas can't break Core.Pizzas.V1.Queries.
Position
Below the diagonal: Api.Endpoints.V1.Pizzas uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
141
High / Critical
A05:2025 — Injection
72
High / Critical
A02:2025 — Security Misconfiguration
38
High / Critical
A07:2025 — Authentication Failures
6
High / Critical
Roadmap
Immediately resolve the three leaked secrets in REDACTED, REDACTED, and REDACTED, then address the twelve deprecated dependencies starting with package.json and AppHost.csproj. Follow this by fixing the two vulnerable dependencies and ensuring the test suite can be installed from its own lockfile. Finally, codify backups and geo-recovery in infrastructure as code while documenting RTO, RPO, and restore procedures to establish true disaster recovery.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED.
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; CONTRIBUTING.md names .NET 9, but the projects target .NET 10; CONTRIBUTING.md runs `dotnet test # For .NET`, but no project, solution or folder named `#` exists; GETTING_STARTED.md names .NET 9, but the projects target .NET 10; GETTING_STARTED.md changes into `Project-Templates/backend/.NET`, but no such folder exists.
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 — 124
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 — 461
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 — 473
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 6
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. 93 of 101 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 8 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 — 101 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, 679 of 1058 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.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 87 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 6 test source file(s) (.java, .py, .ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'frontend/React/Aspire/AppHost.csproj' with message: The referenced project ../../backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Api.csproj does not exist.
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 32 deducted marker(s) and the 0.8/KLoC density on this row were taken over this repository's .NET projects ALONE: .ts (4,315 lines, 92% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 3 task marker(s) (TODO/FIXME/HACK/XXX) across 3 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. 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.
D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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. `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/DatabaseContext.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CompleteOrderCommand.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CreateOrderCommand.cs`, … (+58 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.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AC6 Visual & motion safety — 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
M4 Documentation accuracy — 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. 189 further occurrence(s) are not listed individually; the score already reflects all 229.
PF3 Async & latency hygiene — 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. 42 further occurrence(s) are not listed individually; the score already reflects all 82.
X1 Async correctness — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
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.
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 REDACTED, 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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
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.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (8): D19, D20, D21, D22, D24, D25, 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.
Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 18), (anonymous) (cyclomatic 18), (anonymous) (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 14 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with DependencyInjectionEndPoints.AddV1Endpoint (cognitive 17). — Refactoring it lifts Cognitive Complexity from 9.8 to about 10.0/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes10.0 / 10Exemplary✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
47 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. Measured on part of this repository only: .ts (92% 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.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 Duplicated block (7 lines × 4) finding(s) in Code Duplication — start with UpdatePizzaCommandValidator.cs, Settings.cs, StartupSettings.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (16 lines × 5) finding(s) in Code Duplication — start with LoggingMiddleware.cs, PizzaImageService.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (9 lines × 5) finding(s) in Code Duplication — start with Order.cs, CommonServices.cs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
3 production modules (Maven+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 1 mechanizable ADR(s) are enforced: 1 by analyzers, 0 by tests. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
97 test methods: 94 unit, 3 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 6 `it`/`test` case(s) across 3 test file(s) declaring at least one beside 87 .NET test method(s); its tier split is read from package names and paths only. The Python suite contributes 3 test function(s) across 2 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The java suite(s) contribute 1 test method(s), read from the language model's own test census — every XCTest `test…` method on an XCTestCase, every swift-testing `@Test` and every JUnit/TestNG `@Test`-annotated method, which is those frameworks' own discovery rule. Their tier split is INFERRED from the test target's name and path only, not declared.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, 1 mock references across 87 tests. Measured on the C# suite only — at least 6 test source file(s) (.java, .py, .ts) went unread, so its test quality is unmeasured and is not in these counts.
Mock framework: NSubstitute
✓ On the Gold path — maintain.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 2 measured tier(s). other: measured (0 flaky); JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in backend/Node/ (4 tests); vitest via `npm ci --ignore-scripts` in frontend/React/): measured (0 flaky).
Test suite cannot be installed from its own lockfile: frontend/React/
What to do
Resolve the 1 Test suite cannot be installed from its own lockfile finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d11_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
50 outdated, 2 vulnerable, 7 deprecated, 3 prerelease packages. Those are the NuGet packages; this repository's npm dependencies were read too — 272 outdated of 393 package(s) across 4 lockfile(s).
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 12 Deprecated finding(s) in Dependency Hygiene — start with package.json (5), AppHost.csproj (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 3 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (3 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 452 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 69 direct `PackageReference`(s), and 182 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
32 deducted debt markers + unmeasured dead symbols across 17303 LoC in the .NET projects (0.8/KLoC) → score 8.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .ts (92% of production source) was not read, and carries at least 3 uncounted task marker(s) in 3 file(s).
Resolve the 28 CoverageExclusion finding(s) in Explicit Debt — start with StartupConfiguration.cs (6), LoggingMiddleware.cs (5), StartupSettings.cs (5). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 4 CommentedOutCode finding(s) in Explicit Debt — start with Extensions.cs (4). — One of this dimension's main actionable groups (4 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: 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.
This repository is a comprehensive collection of production-ready templates for building full-stack applications across .NET, React, Angular, and more. The root README gives an excellent overview (production-ready architectures, polyglot support, quick start, community-driven) with a strong rationale section plus a detailed architecture roadmap that lists every visible document in the summary as existing. The repository's documentation is comprehensive and well-organized. The READMEs for each directory (e.g., .NET Template Documentation, Angular OpenAPI Client, frontend/Angular/docs/) are complete within their scope — the .NET/.Angular/.Frontend source directories document what they contain rather than the whole repo — and all visible sections exist in the outline. Architecture/Docs markdown files provide detailed design documentation for 88 documents (e.g., Load Testing with K6, Vertical Slice Template). XML-doc coverage is low (<20%), reflecting a primarily non-XML doc set. (7 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR QualityExemplary◐ Sampled · advisory
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.
Inconsistent naming for the same database column concept ('Name'). Some fields use 'Table.Name' while others use 'Columns.Name'. While 'Table' and 'Columns' might refer to different scopes (table-level vs column-level metadata), the parallel structure suggests 'Columns.Name' is the standard for column definitions, making 'Table.Name' potentially confusing or inconsistent if they refer to the same underlying DB column name.
Inconsistent naming style for client methods. 'Search_for_pizzas' and 'Update_pizza' use snake_case with underscores, whereas the rest of the codebase (e.g., 'CreateAsync', 'DeleteAsync', 'GetAllPizzasQuery') uses PascalCase. This breaks the naming convention for public API methods.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyWeak◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
Three different interfaces named IPizzaDataAccess exist across different namespaces. Two share the same namespace path structure (DataAccess.Contracts.Pizzas.V1 vs Infrastructure.Contracts.Pizzas.V1) and identical signatures, suggesting duplication. The third (DataAccess.Contracts.V1) has a different signature (Result<IEnumerable<PizzaModel>> vs ListResult<PizzaModel>), indicating inconsistent return types for the same operation.
Duplicate interface definition. Both Infrastructure.Contracts.Pizzas.V1.IPizzaDataAccess and DataAccess.Contracts.Pizzas.V1.IPizzaDataAccess have identical method signatures and names. This creates ambiguity about which interface should be consumed.
Inconsistent return types for Search within the same root namespace (DataAccess.Contracts). One uses ListResult<PizzaModel> and the other uses Result<IEnumerable<PizzaModel>>. This forces consumers to handle different result wrappers for the same logical operation.
What to do
Resolve the 1 Three different interfaces named IPizzaDataAccess exist across different… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicate interface definition. Both… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent return types for Search within the same root namespace… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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).
72 finding(s): 0 critical, 21 high, 51 medium, 0 low. 17 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 64 file(s) — `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs` (line 7), `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs` (lines 22–170), `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/DatabaseContext.cs` (line 7), `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CompleteOrderCommand.cs` (line 11), `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CreateOrderCommand.cs` (line 16), … (+59 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 58 of those file(s) — `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/DatabaseContext.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CompleteOrderCommand.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CreateOrderCommand.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Queries/GetOrderStatusQuery.cs`, … (+53 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. In 2 of those file(s) — `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs`, `backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupApp/Services/CommonServices.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 17 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (17 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 71 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (57), REDACTED (8). — One of this dimension's main actionable groups (71 issue-level).
Resolve the 41 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (29), REDACTED (6), REDACTED. — One of this dimension's main actionable groups (41 warning-level).
Resolve the 11 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 22 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (15), REDACTED (7). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 8 High IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 7 Low IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 32 of the 331 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 49 platform declaration(s) and 17 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC2 · Forms & labels5.6 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×4) — frontend/Angular/src/app/features/order/pages/order-page.component.html:81, frontend/Angular/src/app/features/order/pages/order-page.component.html:93, frontend/Angular/src/app/features/order/pages/order-page.component.html:106, …
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — frontend/React/src/features/order/components/ShoppingCartItem.tsx:30
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.
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.
`.input-field:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/Angular/public/css/input.css:125
`form input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/Angular/public/css/style.css:68
`button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/Angular/public/css/style.css:83
`.spinner` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.grid.scss:44
`.pizza-header` moves (`animation: slideDown var(--transition-slower)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:19
`.pizza-card` moves (`animation: popIn var(--transition-slower)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:142
`.pizza-sidebar` moves (`animation: slideInRight var(--transition-base)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:245
`.pizza-header` moves (`animation: slideDown 0.6s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:491
`.pizza-card__image` moves (`transition: transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:643
`.pizza-card` moves (`animation: popIn 0.5s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:622
`.pizza-sidebar` moves (`animation: slideInRight 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:741
`.order-tracking-page__loading .spinner` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/features/order/pages/OrderTrackingPage.scss:222
`.spinner__circle` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/components/ui/Spinner.scss:14
`.image` moves (`transition: transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/components/PizzaCard/PizzaCard.module.scss:43
`.heroContent` moves (`animation: fadeInUp 0.8s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/components/HeroSection/HeroSection.module.scss:51
`.heroLogo` moves (`animation: float 3s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/components/HeroSection/HeroSection.module.scss:61
`.floatingCart--hidden` moves (`animation: slideOut 0.3s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/components/FloatingCart/FloatingCart.module.scss:41
`.floatingCart` moves (`animation: slideIn 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/components/FloatingCart/FloatingCart.module.scss:21
`.hero__logo` moves (`animation: float 3s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/React/src/app/App.module.scss:88
`.card-hover::before` moves (`transition: opacity 200ms ease, transform 200ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×3) — frontend/React/public/theme/css/theme.css:643, frontend/Angular/public/css/input.css:95, frontend/Angular/public/css/theme.css:643
`.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, -webkit-backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — frontend/React/public/theme/css/theme.css:1197, frontend/Angular/public/css/theme.css:1197
`.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — frontend/React/public/theme/css/theme.css:1198, frontend/Angular/public/css/theme.css:1198
`.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter, -webkit-backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — frontend/React/public/theme/css/theme.css:1199, frontend/Angular/public/css/theme.css:1199
`.transition-transform` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — frontend/React/public/theme/css/theme.css:1205, frontend/Angular/public/css/theme.css:1205
`.theme-toggle` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — frontend/React/public/theme/css/theme.css:1484, frontend/Angular/public/css/theme.css:1484
`.skeleton` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/src/styles.scss:209
`.skeleton-image` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/src/styles.scss:223
`.skeleton-title` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/src/styles.scss:236
`.skeleton-text` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/src/styles.scss:250
`.toast-progress` moves (`animation: progress linear forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/src/app/shared/components/toast-banner/toast-banner.component.scss:163
`.fade-in` moves (`animation: fadeIn 0.5s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/public/css/input.css:414
`.slide-up` moves (`animation: slideUp 0.5s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/public/css/input.css:418
`.diamond` moves (`animation: expand 10s infinite ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/Angular/public/css/style.css:184
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 62 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
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`IPizzaClient` declares 18 members under just 12 distinct name(s): `GetImageAsync`, `GetImage`, `GetImageAsync`, `GetAsync`, `Get`, `GetAsync`, `UpdateAsync`, `Update`, `UpdateAsync`, `DeleteAsync`, `Delete`, `DeleteAsync`, `SearchAsync`, `Search`, `SearchAsync`, `CreateAsync`, `Create`, `CreateAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. (×4) — backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:683, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:683, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api.Client/Api-Client-v1.cs:683, …
`IClient` declares 24 members: `GetHcAsync`, `GetHc`, `GetHcAsync`, `Create_a_pizzaAsync`, `Create_a_pizza`, `Create_a_pizzaAsync`, `Update_pizzaAsync`, `Update_pizza`, `Update_pizzaAsync`, `GetPizzaImageAsync`, `GetPizzaImage`, `GetPizzaImageAsync`, `Search_for_pizzasAsync`, `Search_for_pizzas`, `Search_for_pizzasAsync`, `Complete_orderAsync`, `Complete_order`, `Complete_orderAsync`, `Create_orderAsync`, `Create_order`, `Create_orderAsync`, `Get_order_statusAsync`, `Get_order_status`, `Get_order_statusAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:27
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
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.
`OrderMap` (slice 'Orders') depends on `Pizza` from slice 'Pizzas'. — backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Orders/V1/Mapping/OrderMap.cs:52
`CartService` (slice 'order') depends on `Pizza` from slice 'pizza'. — frontend/Angular/src/app/features/order/services/cart.service.ts:54
`PizzaMenuComponent` (slice 'pizza-menu') depends on `CartService` from slice 'order'. — frontend/Angular/src/app/features/pizza-menu/pizza-menu.component.ts:145
`PizzaCardComponent` (slice 'pizza') depends on `CartService` from slice 'order'. (×2) — frontend/Angular/src/app/features/pizza/components/pizza-card/pizza-card.component.ts:132, frontend/Angular/src/app/features/pizza/components/pizza-card/pizza-card.standalone.component.ts:39
`PizzaMenuPageComponent` (slice 'pizza') depends on `CartService` from slice 'order'. — frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts:226
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.
Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`Seed` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Endpoints/V1/Admin/SeedDataEndpoint.cs:7
`Clean` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Endpoints/V1/Admin/SeedDataEndpoint.cs:20
The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseConfiguration.cs:26
What to do
Remove the dead code that still moves this score: delete dead if(false) / #if false branches and either do the real async work or drop the async keyword from fake-async methods.
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.
185 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 46 of 48 project(s) that lack one — worth up to 1.9 pts.
Review the README against recent changes; refresh the parts that drifted.
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.
12 ADR-shaped document(s) detected by content — `docs/ATOMS_COMPLETE.md`, `docs/COMPLETION_DASHBOARD.md`, `docs/OPENAPI_GENERATION_IMPLEMENTATION.md`, `docs/OPENAPI_GENERATION_SETUP_COMPLETE.md`, `docs/PHASE_2_COMPLETION.md`, `docs/REVIEW_STATUS.md`, `docs/SESSION_CONTINUATION_SUMMARY.md`, `docs/SESSION_FINAL_SUMMARY.md`, `docs/SESSION_SUMMARY_NOV_4.md`, `docs/TEMPLATE_REVIEW_SUMMARY.md`, `docs/TRANSFORMATION_COMPLETE.md`, `docs/TRANSFORMATION_SUMMARY.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Only 10/48 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:175
CONTRIBUTING.md names .NET 9, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:48
CONTRIBUTING.md runs `dotnet test # For .NET`, but no project, solution or folder named `#` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:278
GETTING_STARTED.md names .NET 9, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:34
GETTING_STARTED.md changes into `Project-Templates/backend/.NET`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:108
GETTING_STARTED.md changes into `Project-Templates/backend/.NET/1.LayeredArchitecture`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:122
GETTING_STARTED.md changes into `src/MyApp.Api`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:214
GETTING_STARTED.md runs `dotnet test tests/MyApp.Application.Tests`, but `tests/MyApp.Application.Tests` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:355
GETTING_STARTED.md installs the package `MediatR` (`dotnet add MyApp.Application package MediatR`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:365
GETTING_STARTED.md runs `dotnet ef migrations add AddUserTable -p src/MyApp.Infrastructure -s src/MyApp.Api`, but `src/MyApp.Infrastructure` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:378
GETTING_STARTED.md names `MyApp.sln`, but no file or folder `MyApp.sln` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GETTING_STARTED.md:423
README.md links to `./frontend/React/template/GET_STARTED.md`, but `frontend/React/template/GET_STARTED.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:88
README.md links to `./frontend/React/template/docs/`, but `frontend/React/template/docs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:88
README.md links to `./frontend/Angular/template/ANGULAR_README.md`, but `frontend/Angular/template/ANGULAR_README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:93
README.md names .NET 9, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:99
docs/ANGULAR_TEMPLATE_PLAN.md names `tailwind.config.js`, but no file or folder `tailwind.config.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:61
docs/ANGULAR_TEMPLATE_PLAN.md names `src/app/types/index.ts`, but no file or folder `src/app/types/index.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:108
docs/ANGULAR_TEMPLATE_PLAN.md names `src/app/components/atoms/index.ts`, but no file or folder `src/app/components/atoms/index.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:261
docs/ANGULAR_TEMPLATE_PLAN.md names `src/app/services/api.service.ts`, but no file or folder `src/app/services/api.service.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:275
docs/ANGULAR_TEMPLATE_PLAN.md names `clients/generation/openapi-generator-angular.json`, but no file or folder `clients/generation/openapi-generator-angular.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:555
docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/template/README.md`, but no file or folder `frontend/Angular/template/README.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:573
docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/ANGULAR_SETUP_GUIDE.md`, but no file or folder `frontend/Angular/ANGULAR_SETUP_GUIDE.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:579
docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/COMPONENT_LIBRARY.md`, but no file or folder `frontend/Angular/COMPONENT_LIBRARY.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:585
docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/OPENAPI_INTEGRATION.md`, but no file or folder `frontend/Angular/OPENAPI_INTEGRATION.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ANGULAR_TEMPLATE_PLAN.md:591
docs/ATOMS_COMPLETE.md names Sass 2, but the manifest declares `sass` ^1.69.5. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ATOMS_COMPLETE.md:229
docs/BULLETPROOF_REACT_STATUS.md runs `npm run test:e2e # E2E tests`, but no package.json declares a `test:e2e` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/BULLETPROOF_REACT_STATUS.md:258
docs/COMPONENT_REFACTORING.md names `src/components/Form/`, but no file or folder `src/components/Form` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/COMPONENT_REFACTORING.md:9
docs/COMPONENT_REFACTORING.md names `src/components/Button/`, but no file or folder `src/components/Button` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/COMPONENT_REFACTORING.md:51
docs/COMPONENT_REFACTORING.md names `Button.module.scss`, but no file or folder `Button.module.scss` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/COMPONENT_REFACTORING.md:165
docs/CONSOLIDATION_SUMMARY.md names `src/components/Form/`, but no file or folder `src/components/Form` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CONSOLIDATION_SUMMARY.md:135
docs/CONSOLIDATION_SUMMARY.md names `src/components/Button/Button.tsx`, but no file or folder `src/components/Button/Button.tsx` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CONSOLIDATION_SUMMARY.md:136
docs/CONSOLIDATION_SUMMARY.md names `src/components/Button/SubmitButton.tsx`, but no file or folder `src/components/Button/SubmitButton.tsx` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CONSOLIDATION_SUMMARY.md:137
docs/CONSOLIDATION_SUMMARY.md names `src/components/Button/`, but no file or folder `src/components/Button` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CONSOLIDATION_SUMMARY.md:139
docs/EXECUTION_PLAN.md names `frontend/React/template/`, but no file or folder `frontend/React/template` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/EXECUTION_PLAN.md:21
docs/EXECUTION_PLAN.md names `Middleware/ValidationExceptionHandlerMiddleware.cs`, but no file or folder `Middleware/ValidationExceptionHandlerMiddleware.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/EXECUTION_PLAN.md:129
docs/EXECUTION_PLAN.md names `src/features/pizzas/components/CustomerInfoForm.tsx`, but no file or folder `src/features/pizzas/components/CustomerInfoForm.tsx` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/EXECUTION_PLAN.md:211
docs/EXECUTION_PLAN.md names `src/features/pizzas/utils/orderCookie.ts`, but no file or folder `src/features/pizzas/utils/orderCookie.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/EXECUTION_PLAN.md:270
docs/EXECUTION_PLAN.md names `src/features/pizzas/pages/CheckoutPage.tsx`, but no file or folder `src/features/pizzas/pages/CheckoutPage.tsx` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/EXECUTION_PLAN.md:296
docs/EXECUTION_PLAN.md names `src/features/pizzas/pages/OrderTrackingPage.tsx`, but no file or folder `src/features/pizzas/pages/OrderTrackingPage.tsx` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/EXECUTION_PLAN.md:303
docs/EXECUTION_PLAN.md names `shared/components/theme-switcher/theme-switcher.component.ts`, but no file or folder `shared/components/theme-switcher/theme-switcher.component.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/EXECUTION_PLAN.md:461
What to do
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; CONTRIBUTING.md names .NET 9, but the projects target .NET 10; CONTRIBUTING.md runs `dotnet test # For .NET`, but no project, solution or folder named `#` exists; GETTING_STARTED.md names .NET 9, but the projects target .NET 10; GETTING_STARTED.md changes into `Project-Templates/backend/.NET`, but no such folder exists.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning2.0 / 10Weak✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
103/111 types (93%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `backend/Java`, `frontend/Angular`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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.
What to do
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
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
`EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely. (×4) — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:18, backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:151, backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Benchmark.Testing/Setup/DatabaseContextFactory.cs:24, …
What to do
Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 2 use(s) across 18,915 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 (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
44 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×39) — backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:231, backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:355, backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:465, …
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
Do you agree with this assessment?
R1 · Type Safety8.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
frontend/Angular/src/app/shared/components/toast-banner/toast-banner.service.ts:152 · frontend/Angular/src/app/shared/services/toast.service.ts:87 — the two spans are one implementation copied and then locally edited — 123 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. — frontend/Angular/src/app/shared/components/toast-banner/toast-banner.service.ts:152
backend/Java/k6/load.js:4 · backend/Python/k6/load.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — backend/Java/k6/load.js:4
frontend/Angular/src/app/core/observability/opentelemetry.service.ts:407 · frontend/Angular/src/app/core/observability/opentelemetry.service.ts:440 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — frontend/Angular/src/app/core/observability/opentelemetry.service.ts:407
backend/Java/k6/smoke.js:4 · backend/Python/k6/smoke.js:4 — 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. — backend/Java/k6/smoke.js:4
frontend/Angular/src/app/features/order/services/cart.service.ts:179 · frontend/Angular/src/app/features/pizza/services/pizza.service.ts:204 — 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. — frontend/Angular/src/app/features/order/services/cart.service.ts:179
frontend/Angular/src/app/features/order/services/cart.service.ts:18 · frontend/Angular/src/app/features/pizza/services/pizza.service.ts:36 — 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. — frontend/Angular/src/app/features/order/services/cart.service.ts:18
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
loadPizzas has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/Angular/src/app/features/pizza/services/pizza.service.ts:86
Do you agree with this assessment?
R3 · Large Files8.6 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
frontend/Angular/src/app/core/observability/opentelemetry.service.ts has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/Angular/src/app/core/observability/opentelemetry.service.ts:1
frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts has 428 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage4.0 / 10Adequate✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×25) — frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts:1, frontend/Angular/src/app/features/pizza-menu/pizza-menu.component.ts:1, frontend/Angular/src/app/features/pizza/services/pizza.service.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Strong✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code6.2 / 10Adequate✓ 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.
4 file(s) (~66 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
2 file(s) (~32 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — backend/Node
Unreachable from the 5 application, 4 tooling and 3 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 (5 application, 4 tooling, 3 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 (×3) — frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts, frontend/Angular/src/app/shared/services/toast.service.ts, frontend/Angular/src/app/shared/components/toast-banner/index.ts
no import path from any entry point (5 application, 4 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — frontend/Angular/src/app/features/pizza/services/pizza.service.ts, frontend/Angular/src/app/features/pizza/components/pizza-grid/pizza-grid.component.ts
no import path from any entry point (5 application, 4 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/Angular/src/app/features/pizza/components/pizza-grid/pizza-grid.component.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — frontend/Angular/src/app/features/pizza/components/pizza-card/pizza-card.component.ts
Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/Angular/src/app/features/order/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/Angular/src/app/features/order/types/index.ts in the same commit, or the barrel will import a name that no longer exists. — frontend/Angular/src/app/features/order/types/order.interface.ts:103
Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. — frontend/Angular/src/app/features/order/services/cart.service.ts:186
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 backend/Node/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.
Declared in frontend/Angular/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. (×2)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
Set: Permissions-Policy, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.5 on this card.) — backend/.NET/2.CleanArchitecture/Api/StartupApp/App/SecurityApp.cs:9
What to do
Add Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
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. (×40) — backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:231, backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:355, backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:465, …
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 147/180 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken. (×16) — REDACTED:24, backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:37, backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:64, …
No CancellationToken parameter, and the token `request.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `request.HttpContext.RequestAborted` on, or take a CancellationToken. (×3) — backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:83, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:83, backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:78
This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. (×5) — REDACTED:59, REDACTED:62, REDACTED:60, …
No CancellationToken parameter — this work can't be stopped early once started. (×9) — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:12, backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:48, backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:72, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This method contradicts itself about `exception`: line 51 writes `exception?.Message`, which says `exception` can be null, but line 27 then dereferences it directly as `exception.GetType` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — REDACTED:27
This method contradicts itself about `validationException`: line 18 writes `validationException?.Errors`, which says `validationException` can be null, but line 23 then dereferences it directly as `validationException.Errors` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `validationException` truly cannot be null here, the `?.` is misleading. Settle it one way — test `validationException` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/4.Utilities/Handlers/ValidationExceptionHandler.cs:23
This method contradicts itself about `request`: line 24 writes `request?.Name`, which says `request` can be null, but line 28 then dereferences it directly as `request.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Queries/GetAllPizzasQuery.cs:28
This method contradicts itself about `exception`: line 48 writes `exception?.Message`, which says `exception` can be null, but line 33 then dereferences it directly as `exception.Errors` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. (×2) — backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:33, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:33
This method contradicts itself about `model`: line 25 writes `model?.Name`, which says `model` can be null, but line 25 then dereferences it directly as `model.Name` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `model` truly cannot be null here, the `?.` is misleading. Settle it one way — test `model` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Core/Pizzas/V1/Commands/UpdatePizzaCommand.cs:25
This method contradicts itself about `request`: line 20 writes `request?.Name`, which says `request` can be null, but line 25 then dereferences it directly as `request.OrderBy` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:25
This method contradicts itself about `request`: line 23 writes `request?.Name`, which says `request` can be null, but line 27 then dereferences it directly as `request.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:27
This method contradicts itself about `model`: line 19 writes `model?.Name`, which says `model` can be null, but line 23 then dereferences it directly as `model.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `model` truly cannot be null here, the `?.` is misleading. Settle it one way — test `model` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess/V1/Pizzas/PizzaDataAccess.cs:23
This method contradicts itself about `request`: line 22 writes `request?.Name`, which says `request` can be null, but line 26 then dereferences it directly as `request.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:26
This method contradicts itself about `exception`: line 49 writes `exception?.Message`, which says `exception` can be null, but line 34 then dereferences it directly as `exception.Errors` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:34
39/43 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~0.2 `!` suppressions per 1k syntax nodes — 5 suppression(s) across the 32094 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
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
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 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 24 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
D16 Bus Factor — bus factor 1 — one contributor carries this repository
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .java, .py, .ts, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D23 Boundary Type-Coupling — small single-context codebase (5,164 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 63 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the dependency install for frontend/React/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 4 value object(s); its 1 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 4 integration event(s); 43 CQRS handler(s)
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
AC2 · Forms & labels· <input> without a programmatic label · ×4
<input> without a programmatic label frontend/Angular/src/app/features/order/pages/order-page.component.html:81— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/Angular/src/app/features/order/pages/order-page.component.html:93— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/Angular/src/app/features/order/pages/order-page.component.html:106— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label frontend/React/src/features/order/components/ShoppingCartItem.tsx:30— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label frontend/Angular/src/app/features/order/pages/order-page.component.html:118— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
D11 · Test Reliability· Test suite cannot be installed from its own lockfile · ×1
Test suite cannot be installed from its own lockfile: frontend/React/ — The vitest suite in frontend/React/ was never exercised because its dependency install refused the committed lockfile — the dependency install for frontend/React/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
Sync-over-async blocking — 44 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:231— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:355— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:465— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:925— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1023— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1143— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1262— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1366— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1487— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:169— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:245— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:354— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:473— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:566— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:672— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:781— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:890— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:231— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:355— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:465— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:925— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:1023— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:1143— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:1262— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async (deadlock risk) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:231— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:355— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:465— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:925— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1023— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1143— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1262— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1366— 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) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:1487— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:169— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:245— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:354— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:473— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:566— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:672— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:781— 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) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:890— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:231— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:355— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:465— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:925— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:1023— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:1143— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:1262— 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) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:1366— 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.
+ 15 more in this group — see findings.md.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×37
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.grid.scss:44— `.spinner` moves (`animation: spin 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:19— `.pizza-header` moves (`animation: slideDown var(--transition-slower)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:142— `.pizza-card` moves (`animation: popIn var(--transition-slower)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:245— `.pizza-sidebar` moves (`animation: slideInRight var(--transition-base)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:491— `.pizza-header` moves (`animation: slideDown 0.6s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:643— `.pizza-card__image` moves (`transition: transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:622— `.pizza-card` moves (`animation: popIn 0.5s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/pizza/pages/PizzaMenuPage.scss:741— `.pizza-sidebar` moves (`animation: slideInRight 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/features/order/pages/OrderTrackingPage.scss:222— `.order-tracking-page__loading .spinner` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/components/ui/Spinner.scss:14— `.spinner__circle` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/components/PizzaCard/PizzaCard.module.scss:43— `.image` moves (`transition: transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/components/HeroSection/HeroSection.module.scss:51— `.heroContent` moves (`animation: fadeInUp 0.8s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/components/HeroSection/HeroSection.module.scss:61— `.heroLogo` moves (`animation: float 3s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/components/FloatingCart/FloatingCart.module.scss:41— `.floatingCart--hidden` moves (`animation: slideOut 0.3s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/components/FloatingCart/FloatingCart.module.scss:21— `.floatingCart` moves (`animation: slideIn 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/src/app/App.module.scss:88— `.hero__logo` moves (`animation: float 3s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/public/theme/css/theme.css:643— `.card-hover::before` moves (`transition: opacity 200ms ease, transform 200ms ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/public/theme/css/theme.css:1197— `.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, -webkit-backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/public/theme/css/theme.css:1198— `.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/public/theme/css/theme.css:1199— `.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter, -webkit-backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/public/theme/css/theme.css:1205— `.transition-transform` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/React/public/theme/css/theme.css:1484— `.theme-toggle` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/Angular/src/styles.scss:209— `.skeleton` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/Angular/src/styles.scss:223— `.skeleton-image` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/Angular/src/styles.scss:236— `.skeleton-title` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
CoverageExclusion backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:6— class LoggingMiddleware — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:7— class LoggingMiddleware — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:5— class LoggingMiddleware — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:5— class LoggingMiddleware — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:11— class LoggingMiddleware — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupConfiguration.cs:3— class StartupConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/StartupConfiguration.cs:3— class StartupConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/2.CleanArchitecture/Domain/StartupConfiguration.cs:3— class StartupConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/StartupConfiguration.cs:3— class StartupConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupConfiguration.cs:2— class StartupConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupSettings.cs:5— class StartupSettings — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/StartupSettings.cs:5— class StartupSettings — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/2.CleanArchitecture/Domain/StartupSettings.cs:5— class StartupSettings — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/StartupSettings.cs:5— class StartupSettings — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupSettings.cs:5— class StartupSettings — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess/BaseDataAccess.cs:5— class BaseDataAccess — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/Settings.cs:6— class Settings — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupConfiguration.cs:16— class OpenApi — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/Logging/Config/LoggingConfig.cs:2— class LoggingConfig — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/Logging/Config/LoggingConfiguration.cs:3— class LoggingConfiguration — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/Logging/Static/Logger.cs:8— class Logger — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/Logging/Static/LoggerSetup.cs:9— class LoggerSetup — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/Models/Error.cs:5— class Error — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/Models/PagingArgs.cs:2— class PagingArgs — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion backend/.NET/4.Utilities/ProcessEFResult.cs:5— class ProcessEFResult — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
+ 3 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×28
Async method without CancellationToken: HandleExceptionAsync REDACTED:24— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleValidationExceptionAsync backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:37— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleOperationCanceledExceptionAsync backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:64— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleExceptionAsync backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:72— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: FormatRequest backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:83— No CancellationToken parameter, and the token `request.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `request.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleValidationExceptionAsync backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:31— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleOperationCanceledExceptionAsync backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:58— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleExceptionAsync backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:66— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: InitializeAndSeedAsync backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:12— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SeedAsync backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:48— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CleanDataAsync backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:72— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SeedSamplePizzasAsync backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:117— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ResetDatabaseAsync backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:145— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PromptUserForResetAsync backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:162— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PromptUserForConfirmationAsync backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:169— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateCSharpClient backend/.NET/3.VerticalSliceArchitecture/2.Minimal/ClientGenerator/Program.cs:107— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateTypeScriptClient backend/.NET/3.VerticalSliceArchitecture/2.Minimal/ClientGenerator/Program.cs:149— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleValidationExceptionAsync backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:31— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleOperationCanceledExceptionAsync backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:58— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleExceptionAsync backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:66— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleValidationExceptionAsync backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:37— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleOperationCanceledExceptionAsync backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:64— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleExceptionAsync backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:72— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: FormatRequest backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:83— No CancellationToken parameter, and the token `request.HttpContext.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `request.HttpContext.RequestAborted` on, or take a CancellationToken.
Async method without CancellationToken: HandleValidationExceptionAsync backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:32— No CancellationToken parameter, and the token `context.RequestAborted` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `context.RequestAborted` on, or take a CancellationToken.
+ 3 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×25
No test reaches this file frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/features/pizza-menu/pizza-menu.component.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/features/pizza/services/pizza.service.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/public/js/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/telemetry/telemetry.service.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/features/pizza/components/pizza-card/pizza-card.component.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/shared/services/toast.service.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/services/logging.service.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/features/pizza/components/pizza-grid/pizza-grid.component.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/features/order/pages/order-page.component.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/public/js/theme.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/server.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/services/loading.service.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/services/notification.service.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/interceptors/error.interceptor.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file backend/Java/k6/load.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file backend/Python/k6/load.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/interceptors/loading.interceptor.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/telemetry/telemetry.provider.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/core/interceptors/auth.interceptor.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/app/app.routes.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file backend/Java/k6/smoke.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file backend/Python/k6/smoke.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/main.server.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/Angular/src/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Deprecated: Aspire.Dashboard.Sdk.linux-x64 — Aspire.Dashboard.Sdk.linux-x64 [13.0.0, — ) — the publisher's replacement is `13.0.0` Other,Legacy; migrate the reference to it.
Deprecated: Aspire.Hosting.Orchestration.linux-x64 — Aspire.Hosting.Orchestration.linux-x64 [13.0.0, — ) — the publisher's replacement is `13.0.0` Other,Legacy; 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: supertest backend/Node/package.json:29— supertest 6.3.4, declared in backend/Node/package.json, is marked deprecated by its publisher: "Please upgrade to supertest v7.1.3+, see release notes at https://github.com/forwardemail/supertest/releases/tag/v7.1.3 - maintenance is supported by Forward Email @ https://forwardemail.net". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint backend/Node/package.json:32— eslint 8.57.1, declared in backend/Node/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @angular/animations frontend/Angular/package.json:32— @angular/animations 21.0.0, declared in frontend/Angular/package.json, is marked deprecated by its publisher: "@angular/animations is deprecated. Use `animate.enter` and `animate.leave` instead. For more information see: https://v22.angular.dev/guide/animations.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @opentelemetry/sdk-trace-web frontend/Angular/package.json:54— @opentelemetry/sdk-trace-web 2.2.0, declared in frontend/Angular/package.json, is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint frontend/React/package.json:61— eslint 8.57.1, declared in frontend/React/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×11
Symbol treated as nullable, then dereferenced unguarded REDACTED:27— This method contradicts itself about `exception`: line 51 writes `exception?.Message`, which says `exception` can be null, but line 27 then dereferences it directly as `exception.GetType` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/4.Utilities/Handlers/ValidationExceptionHandler.cs:23— This method contradicts itself about `validationException`: line 18 writes `validationException?.Errors`, which says `validationException` can be null, but line 23 then dereferences it directly as `validationException.Errors` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `validationException` truly cannot be null here, the `?.` is misleading. Settle it one way — test `validationException` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Queries/GetAllPizzasQuery.cs:28— This method contradicts itself about `request`: line 24 writes `request?.Name`, which says `request` can be null, but line 28 then dereferences it directly as `request.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:33— This method contradicts itself about `exception`: line 48 writes `exception?.Message`, which says `exception` can be null, but line 33 then dereferences it directly as `exception.Errors` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Core/Pizzas/V1/Commands/UpdatePizzaCommand.cs:25— This method contradicts itself about `model`: line 25 writes `model?.Name`, which says `model` can be null, but line 25 then dereferences it directly as `model.Name` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `model` truly cannot be null here, the `?.` is misleading. Settle it one way — test `model` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:25— This method contradicts itself about `request`: line 20 writes `request?.Name`, which says `request` can be null, but line 25 then dereferences it directly as `request.OrderBy` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:27— This method contradicts itself about `request`: line 23 writes `request?.Name`, which says `request` can be null, but line 27 then dereferences it directly as `request.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:33— This method contradicts itself about `exception`: line 48 writes `exception?.Message`, which says `exception` can be null, but line 33 then dereferences it directly as `exception.Errors` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess/V1/Pizzas/PizzaDataAccess.cs:23— This method contradicts itself about `model`: line 19 writes `model?.Name`, which says `model` can be null, but line 23 then dereferences it directly as `model.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `model` truly cannot be null here, the `?.` is misleading. Settle it one way — test `model` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:26— This method contradicts itself about `request`: line 22 writes `request?.Name`, which says `request` can be null, but line 26 then dereferences it directly as `request.PagingArgs` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `request` truly cannot be null here, the `?.` is misleading. Settle it one way — test `request` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:34— This method contradicts itself about `exception`: line 49 writes `exception?.Message`, which says `exception` can be null, but line 34 then dereferences it directly as `exception.Errors` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
(anonymous) (cyclomatic 18) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/k6/comprehensive-all-endpoints.js:54— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 33 function items inside it that branch (a function literal at line 101, a function literal at line 198, (anonymous)::Delete: 200/204/404, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 18) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/k6/comprehensive-all-endpoints.js:54— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 33 function items inside it that branch (a function literal at line 101, a function literal at line 198, (anonymous)::Delete: 200/204/404, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 18) backend/.NET/2.CleanArchitecture/LoadTesting/k6/comprehensive-all-endpoints.js:54— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 33 function items inside it that branch (a function literal at line 101, a function literal at line 198, (anonymous)::Delete: 200/204/404, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 18) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/LoadTesting/k6/comprehensive-all-endpoints.js:54— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 33 function items inside it that branch (a function literal at line 101, a function literal at line 198, (anonymous)::Delete: 200/204/404, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 18) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/comprehensive-all-endpoints.js:54— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 33 function items inside it that branch (a function literal at line 101, a function literal at line 198, (anonymous)::Delete: 200/204/404, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 18) backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/comprehensive-all-endpoints.js:54— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 33 function items inside it that branch (a function literal at line 101, a function literal at line 198, (anonymous)::Delete: 200/204/404, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 18) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/comprehensive-all-endpoints.js:54— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 33 function items inside it that branch (a function literal at line 101, a function literal at line 198, (anonymous)::Delete: 200/204/404, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 16) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/k6/order-endpoints.js:46— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 50, (anonymous)::Create order: has order id, (anonymous)::Create order: status 200/201, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 16) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/k6/order-endpoints.js:46— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 50, (anonymous)::Create order: has order id, (anonymous)::Create order: status 200/201, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 16) backend/.NET/2.CleanArchitecture/LoadTesting/k6/order-endpoints.js:46— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 50, (anonymous)::Create order: has order id, (anonymous)::Create order: status 200/201, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 16) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/LoadTesting/k6/order-endpoints.js:46— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 50, (anonymous)::Create order: has order id, (anonymous)::Create order: status 200/201, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 16) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/order-endpoints.js:46— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 50, (anonymous)::Create order: has order id, (anonymous)::Create order: status 200/201, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 16) backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/order-endpoints.js:46— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 50, (anonymous)::Create order: has order id, (anonymous)::Create order: status 200/201, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 16) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js:46— (anonymous) has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 29 function items inside it that branch (a function literal at line 50, (anonymous)::Create order: has order id, (anonymous)::Create order: status 200/201, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Cross-slice coupling: Orders → Pizzas backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Orders/V1/Mapping/OrderMap.cs:52— `OrderMap` (slice 'Orders') depends on `Pizza` from slice 'Pizzas'.
Cross-slice coupling: order → pizza frontend/Angular/src/app/features/order/services/cart.service.ts:54— `CartService` (slice 'order') depends on `Pizza` from slice 'pizza'.
Cross-slice coupling: pizza-menu → order frontend/Angular/src/app/features/pizza-menu/pizza-menu.component.ts:145— `PizzaMenuComponent` (slice 'pizza-menu') depends on `CartService` from slice 'order'.
Cross-slice coupling: pizza → order frontend/Angular/src/app/features/pizza/components/pizza-card/pizza-card.component.ts:132— `PizzaCardComponent` (slice 'pizza') depends on `CartService` from slice 'order'.
Cross-slice coupling: pizza → order frontend/Angular/src/app/features/pizza/components/pizza-card/pizza-card.standalone.component.ts:39— `PizzaCardComponent` (slice 'pizza') depends on `CartService` from slice 'order'.
Cross-slice coupling: pizza → order frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts:226— `PizzaMenuPageComponent` (slice 'pizza') depends on `CartService` from slice 'order'.
Async endpoint handler without CancellationToken: /hc REDACTED:59— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /hc REDACTED:62— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /hc REDACTED:60— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /hc REDACTED:62— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
Async endpoint handler without CancellationToken: /hc REDACTED:60— This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
P8 · Schema migrations· Schema created with EnsureCreated() (no migration path) · ×4
Schema created with EnsureCreated() (no migration path) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:18— `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseSeeding.cs:151— `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Benchmark.Testing/Setup/DatabaseContextFactory.cs:24— `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Schema created with EnsureCreated() (no migration path) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Benchmark.Testing/Setup/DatabaseContextFactory.cs:39— `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement frontend/Angular/public/css/input.css:125— `.input-field:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/Angular/public/css/style.css:68— `form input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement frontend/Angular/public/css/style.css:83— `button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Prerelease dependency: Microsoft.VisualStudio.Azure.Containers.Tools.Targets — Microsoft.VisualStudio.Azure.Containers.Tools.Targets resolves to 1.23.0-preview.4, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: OpenTelemetry.Instrumentation.EntityFrameworkCore — OpenTelemetry.Instrumentation.EntityFrameworkCore resolves to 1.10.0-beta.1, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Prerelease dependency: NUnit3TestAdapter — NUnit3TestAdapter resolves to 6.0.0-beta.1, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Duplicated block (7 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/UpdatePizzaCommandValidator.cs:7— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/UpdatePizzaCommandValidator.cs:7-13 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Core/V1/Pizzas/Commands/UpdatePizzaCommandValidator.cs:6-12 | backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Commands/UpdatePizzaCommandValidator.cs:6-12 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Commands/UpdatePizzaCommandValidator.cs:6-12 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Core/V1/Pizzas/Commands/UpdatePizzaCommandValidator.cs` and `backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Commands/UpdatePizzaCommandValidator.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Settings.cs:13— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Settings.cs:13-19 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Settings.cs:13-19 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Settings.cs:13-19 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/Settings.cs:15-21 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Settings.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Settings.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupSettings.cs:14— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupSettings.cs:14-20 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/StartupSettings.cs:14-20 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/StartupSettings.cs:14-20 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupSettings.cs:14-20 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupSettings.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/StartupSettings.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:15— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:15-30 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:20-35 | backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:14-29 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:14-29 | backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:20-35 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 4 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:15` 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 (16 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:12— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:12-27 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Services/PizzaImageService.cs:10-25 | backend/.NET/2.CleanArchitecture/Api/Services/PizzaImageService.cs:10-25 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Services/PizzaImageService.cs:10-25 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Services/PizzaImageService.cs:10-25 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Services/PizzaImageService.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/V1/Orders/Order.cs:5— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/V1/Orders/Order.cs:5-13 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/V1/Orders/Order.cs:5-13 | backend/.NET/2.CleanArchitecture/Domain/V1/Orders/Order.cs:4-12 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Orders/V1/Entities/Order.cs:4-12 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Core/Orders/V1/Database/Entities/Order.cs:7-15 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/V1/Orders/Order.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/V1/Orders/Order.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 (9 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs:52— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs:52-60 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/CommonServices.cs:52-60 | backend/.NET/2.CleanArchitecture/Api/StartupApp/Services/CommonServices.cs:52-60 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/StartupApp/Services/CommonServices.cs:51-59 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupApp/Services/CommonServices.cs:65-73 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/CommonServices.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Queries/GetOrderStatusQuery.cs:14— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Queries/GetOrderStatusQuery.cs:14-23 | backend/.NET/2.CleanArchitecture/Application/Orders/V1/Queries/GetOrderStatusQuery.cs:14-23 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Orders/V1/Queries/GetOrderStatusQuery.cs:15-24 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Queries/GetOrderStatusQuery.cs` and `backend/.NET/2.CleanArchitecture/Application/Orders/V1/Queries/GetOrderStatusQuery.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 3) REDACTED:119— REDACTED:119-128 | REDACTED:119-128 | REDACTED:119-128 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:17— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:17-24 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs:17-24 | backend/.NET/2.CleanArchitecture/Domain/Extensions/EnumExtensions.cs:17-24 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Extensions/EnumExtensions.cs:17-24 | backend/.NET/4.Utilities/Extensions/EnumExtensions.cs:18-25 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:17` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:69— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:69-76 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:74-81 | backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:68-75 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:68-75 | backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:74-81 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/UpdatePizzaCommand.cs:25— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/UpdatePizzaCommand.cs:25-31 | backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Commands/UpdatePizzaCommand.cs:25-31 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Commands/UpdatePizzaCommand.cs:27-33 — 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/UpdatePizzaCommand.cs:25` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (7 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:80— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:80-86 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:85-91 | backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:85-91 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess.Contracts/Pizzas/V1/IPizzaDataAccess.cs:11— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess.Contracts/Pizzas/V1/IPizzaDataAccess.cs:11-15 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess.Contracts/V1/IPizzaDataAccess.cs:11-15 | backend/.NET/2.CleanArchitecture/Infrastructure.Contracts/Pizzas/V1/IPizzaDataAccess.cs:11-15 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess.Contracts/Pizzas/V1/IPizzaDataAccess.cs` and `backend/.NET/2.CleanArchitecture/Infrastructure.Contracts/Pizzas/V1/IPizzaDataAccess.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:61— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:61-65 | backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:60-64 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:60-64 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Fake-async — async method never awaits backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Endpoints/V1/Admin/SeedDataEndpoint.cs:7— `Seed` 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 backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Endpoints/V1/Admin/SeedDataEndpoint.cs:20— `Clean` 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 (7 lines × 2 locations) backend/Java/k6/smoke.js:4— backend/Java/k6/smoke.js:4 · backend/Python/k6/smoke.js:4 — 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 (7 lines × 2 locations) frontend/Angular/src/app/features/order/services/cart.service.ts:179— frontend/Angular/src/app/features/order/services/cart.service.ts:179 · frontend/Angular/src/app/features/pizza/services/pizza.service.ts:204 — 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.
bus factor 1 — one contributor carries this repository — 2 contributor(s) have commits in this repository (automation and bot accounts excluded), but the commits of a single one of them cover most of its history — 94% of the 130 commit(s) sampled — so the number of people who actually carry it is 1. This is not the ambient state of a solo project: there ARE other contributors, and if the one who carries the repository becomes unavailable, the knowledge behind most of its history goes with them. Spread the next changes deliberately — have a second contributor review or pair on them — and write down the parts only one person can currently change.
DependencyInjectionEndPoints.AddV1Endpoint (cognitive 17) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Endpoints/DependencyInjectionEndPoints.cs:19— DependencyInjectionEndPoints.AddV1Endpoint has cognitive complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D22 · Internal API Consistency· Three different interfaces named IPizzaDataAccess exist across different namespaces. Two share the same namespace path structure (DataAccess.Contracts.Pizzas.V1 vs Infrastructure.Contracts.Pizzas.V1) and identical signatures, suggesting duplication. The third (DataAccess.Contracts.V1) has a different signature (Result<IEnumerable<PizzaModel>> vs ListResult<PizzaModel>), indicating inconsistent return types for the same operation. · ×1
Three different interfaces named IPizzaDataAccess exist across different namespaces. Two share the same namespace path structure (DataAccess.Contracts.Pizzas.V1 vs Infrastructure.Contracts.Pizzas.V1) and identical signatures, suggesting duplication. The third (DataAccess.Contracts.V1) has a different signature (Result<IEnumerable<PizzaModel>> vs ListResult<PizzaModel>), indicating inconsistent return types for the same operation. — Consolidate into a single IPizzaDataAccess interface. Decide on a standard return type for Search (ListResult vs Result<IEnumerable>) and apply it universally. Remove the duplicate interface in Infrastructure.Contracts if it is merely a copy of the one in DataAccess.Contracts. (signatures: Infrastructure.Contracts.Pizzas.V1.IPizzaDataAccess.Search(PizzaSearchModel model) -> Task<ListResult<PizzaModel>> | DataAccess.Contracts.Pizzas.V1.IPizzaDataAccess.Search(PizzaSearchModel model) -> Task<ListResult<PizzaModel>> | DataAccess.Contracts.V1.IPizzaDataAccess.Search(PizzaSearchModel model) -> Task<Result<IEnumerable<PizzaModel>>>)
D22 · Internal API Consistency· Duplicate interface definition. Both Infrastructure.Contracts.Pizzas.V1.IPizzaDataAccess and DataAccess.Contracts.Pizzas.V1.IPizzaDataAccess have identical method signatures and names. This creates ambiguity about which interface should be consumed. · ×1
Duplicate interface definition. Both Infrastructure.Contracts.Pizzas.V1.IPizzaDataAccess and DataAccess.Contracts.Pizzas.V1.IPizzaDataAccess have identical method signatures and names. This creates ambiguity about which interface should be consumed. — Remove one of the duplicate interfaces. Typically, domain contracts should reside in a shared or domain layer, not duplicated in infrastructure and data access layers unless there is a specific reason (e.g., different method sets, which is not the case here). (signatures: Infrastructure.Contracts.Pizzas.V1.IPizzaDataAccess | DataAccess.Contracts.Pizzas.V1.IPizzaDataAccess)
D22 · Internal API Consistency· Inconsistent return types for Search within the same root namespace (DataAccess.Contracts). One uses ListResult<PizzaModel> and the other uses Result<IEnumerable<PizzaModel>>. This forces consumers to handle different result wrappers for the same logical operation. · ×1
Inconsistent return types for Search within the same root namespace (DataAccess.Contracts). One uses ListResult<PizzaModel> and the other uses Result<IEnumerable<PizzaModel>>. This forces consumers to handle different result wrappers for the same logical operation. — Standardize the return type for Search across all IPizzaDataAccess interfaces. Prefer ListResult<T> if pagination/metadata is needed, or Result<IEnumerable<T>> if not, but ensure consistency. (signatures: DataAccess.Contracts.V1.IPizzaDataAccess.Search | DataAccess.Contracts.Pizzas.V1.IPizzaDataAccess.Search)
D4 · Code Duplication· Near-duplicate member family (4 members, 52 shared lines) · ×1
Near-duplicate member family (4 members, 52 shared lines) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs:27— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs:27-163 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/CommonServices.cs:27-159 | backend/.NET/2.CleanArchitecture/Api/StartupApp/Services/CommonServices.cs:27-159 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/StartupApp/Services/CommonServices.cs:26-154 — These 4 members are variants of one another: a block of 52 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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 (47 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Database/EFMapping/OrderMap.cs:10— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Database/EFMapping/OrderMap.cs:10-56 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess/Mapping/OrderMap.cs:10-56 | backend/.NET/2.CleanArchitecture/Infrastructure/Mapping/OrderMap.cs:10-56 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Orders/V1/Mapping/OrderMap.cs:10-56 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Database/EFMapping/OrderMap.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess/Mapping/OrderMap.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 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `Microsoft.EntityFrameworkCore.Metadata.Builders.EntityTypeBuilder<Order>` in one and `EntityTypeBuilder<Order>` 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 (46–48 lines × 4) REDACTED:18— REDACTED:18-63 | REDACTED:18-65 | REDACTED:17-62 | REDACTED:18-63 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 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 `REDACTED:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (43 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs:81— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs:81-123 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/CommonServices.cs:81-123 | backend/.NET/2.CleanArchitecture/Api/StartupApp/Services/CommonServices.cs:81-123 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/StartupApp/Services/CommonServices.cs:80-122 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/CommonServices.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs:125` calls `AddServiceDiscovery`, `ConfigureHttpClientDefaults` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/CommonServices.cs:125` 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 (40 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/App/SecurityApp.cs:7— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/App/SecurityApp.cs:7-46 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/App/SecurityApp.cs:7-46 | backend/.NET/2.CleanArchitecture/Api/StartupApp/App/SecurityApp.cs:7-46 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/StartupApp/App/SecurityApp.cs:7-46 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupApp/App/SecurityApp.cs:10-49 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/App/SecurityApp.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/App/SecurityApp.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (32–34 lines × 5) REDACTED:18— REDACTED:18-49 | REDACTED:18-51 | REDACTED:17-48 | REDACTED:18-49 | REDACTED:23-54 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 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 `REDACTED:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 `app` to `this IApplicationBuilder` in one and `this WebApplication` 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, `REDACTED:49` calls `UseEndpoints` and `REDACTED:54` 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 × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Database/EFMapping/PizzaMap.cs:9— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Database/EFMapping/PizzaMap.cs:9-37 | backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess/Mapping/PizzaMap.cs:9-37 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess/Mapping/PizzaMap.cs:9-37 | backend/.NET/2.CleanArchitecture/Infrastructure/Mapping/PizzaMap.cs:9-37 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Mapping/PizzaMap.cs:9-37 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Database/EFMapping/PizzaMap.cs` and `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess/Mapping/PizzaMap.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `Microsoft.EntityFrameworkCore.Metadata.Builders.EntityTypeBuilder<Pizza>` in one and `EntityTypeBuilder<Pizza>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (24 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:34— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:34-57 | backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:33-56 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:33-56 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24 lines × 2) backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:39— backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:39-62 | backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:39-62 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:35— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:35-57 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:40-62 | backend/.NET/2.CleanArchitecture/Api/Middleware/LoggingMiddleware.cs:34-56 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Middleware/LoggingMiddleware.cs:34-56 | backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:40-62 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 4 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs:35` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `exception` to `ValidationException` in one and `Exception` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (22 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupConfiguration.cs:3— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupConfiguration.cs:3-24 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/StartupConfiguration.cs:3-24 | backend/.NET/2.CleanArchitecture/Domain/StartupConfiguration.cs:3-24 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/StartupConfiguration.cs:3-24 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupConfiguration.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/StartupConfiguration.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/StartupConfiguration.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 (20 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/Extensions.cs:7— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/Extensions.cs:7-26 | backend/.NET/2.CleanArchitecture/Domain/Extensions/Extensions.cs:7-26 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Extensions/Extensions.cs:7-26 | backend/.NET/4.Utilities/Extensions/Extensions.cs:33-52 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/Extensions.cs` and `backend/.NET/2.CleanArchitecture/Domain/Extensions/Extensions.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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19–20 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/SecurityServices.cs:6— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/SecurityServices.cs:6-24 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/SecurityServices.cs:6-24 | backend/.NET/2.CleanArchitecture/Api/StartupApp/Services/SecurityServices.cs:6-24 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/StartupApp/Services/SecurityServices.cs:6-24 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Common/StartupApp/Services/SecurityServices.cs:9-28 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/SecurityServices.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/StartupApp/Services/SecurityServices.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CreateOrderCommandValidator.cs:7— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CreateOrderCommandValidator.cs:7-24 | backend/.NET/2.CleanArchitecture/Application/Orders/V1/Commands/CreateOrderCommandValidator.cs:7-24 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Orders/V1/Commands/CreateOrderCommandValidator.cs:7-24 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CreateOrderCommandValidator.cs` and `backend/.NET/2.CleanArchitecture/Application/Orders/V1/Commands/CreateOrderCommandValidator.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/DependencyInjection.cs:25— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/DependencyInjection.cs:25-40 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Core/DependencyInjection.cs:26-41 | backend/.NET/2.CleanArchitecture/Application/DependencyInjection.cs:23-38 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/DependencyInjection.cs:24-39 — 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/DependencyInjection.cs:25` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:47— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:47-61 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Services/PizzaImageService.cs:45-59 | backend/.NET/2.CleanArchitecture/Api/Services/PizzaImageService.cs:45-59 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Services/PizzaImageService.cs:45-59 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Services/PizzaImageService.cs:45-59 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Services/PizzaImageService.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 4) REDACTED:20— REDACTED:20-34 | REDACTED:21-35 | REDACTED:21-35 | REDACTED:21-35 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Commands/UpdatePizzaCommand.cs:17— backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Commands/UpdatePizzaCommand.cs:17-30 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Commands/UpdatePizzaCommand.cs:19-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 (12–13 lines × 5) REDACTED:51— REDACTED:51-63 | REDACTED:53-65 | REDACTED:50-62 | REDACTED:51-63 | REDACTED:54-65 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 95 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 `REDACTED: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. 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, `REDACTED:49` calls `UseEndpoints` and `REDACTED:52` 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 (13 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:21— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:21-33 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs:21-33 | backend/.NET/2.CleanArchitecture/Domain/Extensions/EnumExtensions.cs:21-33 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Extensions/EnumExtensions.cs:21-33 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:21` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/V1/Orders/Models/OrderModel.cs:5— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/V1/Orders/Models/OrderModel.cs:5-15 | backend/.NET/2.CleanArchitecture/Domain/V1/Orders/Models/OrderModel.cs:5-15 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Orders/V1/Models/OrderModel.cs:5-15 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Core/Orders/V1/Models/OrderModel.cs:5-15 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/V1/Orders/Models/OrderModel.cs` and `backend/.NET/2.CleanArchitecture/Domain/V1/Orders/Models/OrderModel.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 (11 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/DeletePizzaCommand.cs:12— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/DeletePizzaCommand.cs:12-22 | backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Commands/DeletePizzaCommand.cs:12-22 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Commands/DeletePizzaCommand.cs:15-25 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Commands/DeletePizzaCommand.cs` and `backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Commands/DeletePizzaCommand.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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess.Contracts/Pizzas/V1/IPizzaDataAccess.cs:5— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess.Contracts/Pizzas/V1/IPizzaDataAccess.cs:5-15 | backend/.NET/2.CleanArchitecture/Infrastructure.Contracts/Pizzas/V1/IPizzaDataAccess.cs:5-15 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess.Contracts/Pizzas/V1/IPizzaDataAccess.cs` and `backend/.NET/2.CleanArchitecture/Infrastructure.Contracts/Pizzas/V1/IPizzaDataAccess.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/DataAccess.Contracts/Pizzas/V1/IPizzaDataAccess.cs:5` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:20— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:20-28 | backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Queries/GetAllPizzasQuery.cs:22-30 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:21-29 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:21— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:21-28 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/DataAccess/V1/Pizzas/PizzaDataAccess.cs:18-25 | backend/.NET/2.CleanArchitecture/Application/Pizzas/V1/Queries/GetAllPizzasQuery.cs:23-30 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:22-29 — 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 `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Pizzas/V1/Queries/GetAllPizzasQuery.cs:21` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Helpers/DispatcherExtensions.cs:14— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Helpers/DispatcherExtensions.cs:14-19 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Helpers/DispatcherExtensions.cs:14-19 | backend/.NET/2.CleanArchitecture/Api/Helpers/DispatcherExtensions.cs:14-19 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Helpers/DispatcherExtensions.cs:14-19 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Helpers/DispatcherExtensions.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Helpers/DispatcherExtensions.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (74 lines × 4) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/AspireHost/Extensions.cs:45— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/AspireHost/Extensions.cs:45-118 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/AspireHost/Extensions.cs:45-118 | backend/.NET/2.CleanArchitecture/AspireHost/Extensions.cs:45-118 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/AspireHost/Extensions.cs:45-118 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/AspireHost/Extensions.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/AspireHost/Extensions.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) backend/.NET/2.CleanArchitecture/Api/Program.cs:17— backend/.NET/2.CleanArchitecture/Api/Program.cs:17-24 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Program.cs:17-24 — before extracting anything, compare `backend/.NET/2.CleanArchitecture/Api/Program.cs` and `backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/CommonConfigurationBuilder.cs:9— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/CommonConfigurationBuilder.cs:9-25 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/CommonConfigurationBuilder.cs:9-25 | backend/.NET/2.CleanArchitecture/Domain/CommonConfigurationBuilder.cs:9-25 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/CommonConfigurationBuilder.cs:9-25 | backend/.NET/4.Utilities/CommonConfigurationBuilder.cs:9-25 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/CommonConfigurationBuilder.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/CommonConfigurationBuilder.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:40— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs:40-45 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs:40-45 | backend/.NET/2.CleanArchitecture/Domain/Extensions/EnumExtensions.cs:40-45 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Extensions/EnumExtensions.cs:40-45 | backend/.NET/4.Utilities/Extensions/EnumExtensions.cs:43-48 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:66— backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs:66-70 | backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs:66-70 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Middleware/LoggingMiddleware.cs` and `backend/.NET/4.Utilities/Middleware/LoggingMiddleware.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 83 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 4) REDACTED:105— REDACTED:105-114 | REDACTED:106-115 | REDACTED:106-115 | REDACTED:106-115 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 (5 lines × 5) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:30— backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:30-34 | backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Services/PizzaImageService.cs:28-32 | backend/.NET/2.CleanArchitecture/Api/Services/PizzaImageService.cs:28-32 | backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Services/PizzaImageService.cs:28-32 | backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Services/PizzaImageService.cs:28-32 — before extracting anything, compare `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs` and `backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Services/PizzaImageService.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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.
Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — the dependency install for frontend/React/ refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Infrastructure/DatabaseConfiguration.cs:26— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 185 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
R10 · Code Duplication· Duplicated block with local edits (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) frontend/Angular/src/app/shared/components/toast-banner/toast-banner.service.ts:152— frontend/Angular/src/app/shared/components/toast-banner/toast-banner.service.ts:152 · frontend/Angular/src/app/shared/services/toast.service.ts:87 — the two spans are one implementation copied and then locally edited — 123 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 (17 lines × 2 locations) backend/Java/k6/load.js:4— backend/Java/k6/load.js:4 · backend/Python/k6/load.js:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (16 lines × 2 locations) frontend/Angular/src/app/core/observability/opentelemetry.service.ts:407— frontend/Angular/src/app/core/observability/opentelemetry.service.ts:407 · frontend/Angular/src/app/core/observability/opentelemetry.service.ts:440 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (6 lines × 2 locations) frontend/Angular/src/app/features/order/services/cart.service.ts:18— frontend/Angular/src/app/features/order/services/cart.service.ts:18 · frontend/Angular/src/app/features/pizza/services/pizza.service.ts:36 — 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.
Complex function loadPizzas (cyclomatic 11, cognitive 10) frontend/Angular/src/app/features/pizza/services/pizza.service.ts:86— loadPizzas has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· frontend/Angular/src/app/core/observability/opentelemetry.service.ts · ×1
frontend/Angular/src/app/core/observability/opentelemetry.service.ts: 489 lines of code frontend/Angular/src/app/core/observability/opentelemetry.service.ts:1— frontend/Angular/src/app/core/observability/opentelemetry.service.ts has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts · ×1
frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts: 428 lines of code frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts:1— frontend/Angular/src/app/features/order/components/order-modal/order-modal.component.ts has 428 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~363 LoC) frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts— no import path from any entry point (5 application, 4 tooling, 3 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 (~251 LoC) frontend/Angular/src/app/features/pizza/services/pizza.service.ts— no import path from any entry point (5 application, 4 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~171 LoC) frontend/Angular/src/app/features/pizza/components/pizza-card/pizza-card.component.ts— no import path from any entry point (5 application, 4 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/Angular/src/app/features/pizza/components/pizza-grid/pizza-grid.component.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~124 LoC) frontend/Angular/src/app/shared/services/toast.service.ts— no import path from any entry point (5 application, 4 tooling, 3 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 (~110 LoC) frontend/Angular/src/app/features/pizza/components/pizza-grid/pizza-grid.component.ts— no import path from any entry point (5 application, 4 tooling, 3 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (frontend/Angular/src/app/features/pizza/pages/pizza-menu-page/pizza-menu-page.component.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~11 LoC) frontend/Angular/src/app/shared/components/toast-banner/index.ts— no import path from any entry point (5 application, 4 tooling, 3 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 'pino-http' — Declared in backend/Node/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 '@openapitools/openapi-generator-cli' — Declared in frontend/Angular/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 'run-script-os' — Declared in frontend/Angular/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
README/code drift README.md:175— README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:48— CONTRIBUTING.md names .NET 9, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift CONTRIBUTING.md:278— CONTRIBUTING.md runs `dotnet test # For .NET`, but no project, solution or folder named `#` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:34— GETTING_STARTED.md names .NET 9, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:108— GETTING_STARTED.md changes into `Project-Templates/backend/.NET`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:122— GETTING_STARTED.md changes into `Project-Templates/backend/.NET/1.LayeredArchitecture`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:214— GETTING_STARTED.md changes into `src/MyApp.Api`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:355— GETTING_STARTED.md runs `dotnet test tests/MyApp.Application.Tests`, but `tests/MyApp.Application.Tests` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:365— GETTING_STARTED.md installs the package `MediatR` (`dotnet add MyApp.Application package MediatR`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:378— GETTING_STARTED.md runs `dotnet ef migrations add AddUserTable -p src/MyApp.Infrastructure -s src/MyApp.Api`, but `src/MyApp.Infrastructure` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GETTING_STARTED.md:423— GETTING_STARTED.md names `MyApp.sln`, but no file or folder `MyApp.sln` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:88— README.md links to `./frontend/React/template/GET_STARTED.md`, but `frontend/React/template/GET_STARTED.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:88— README.md links to `./frontend/React/template/docs/`, but `frontend/React/template/docs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:93— README.md links to `./frontend/Angular/template/ANGULAR_README.md`, but `frontend/Angular/template/ANGULAR_README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:99— README.md names .NET 9, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:61— docs/ANGULAR_TEMPLATE_PLAN.md names `tailwind.config.js`, but no file or folder `tailwind.config.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:108— docs/ANGULAR_TEMPLATE_PLAN.md names `src/app/types/index.ts`, but no file or folder `src/app/types/index.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:261— docs/ANGULAR_TEMPLATE_PLAN.md names `src/app/components/atoms/index.ts`, but no file or folder `src/app/components/atoms/index.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:275— docs/ANGULAR_TEMPLATE_PLAN.md names `src/app/services/api.service.ts`, but no file or folder `src/app/services/api.service.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:555— docs/ANGULAR_TEMPLATE_PLAN.md names `clients/generation/openapi-generator-angular.json`, but no file or folder `clients/generation/openapi-generator-angular.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:573— docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/template/README.md`, but no file or folder `frontend/Angular/template/README.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:579— docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/ANGULAR_SETUP_GUIDE.md`, but no file or folder `frontend/Angular/ANGULAR_SETUP_GUIDE.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:585— docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/COMPONENT_LIBRARY.md`, but no file or folder `frontend/Angular/COMPONENT_LIBRARY.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ANGULAR_TEMPLATE_PLAN.md:591— docs/ANGULAR_TEMPLATE_PLAN.md names `frontend/Angular/OPENAPI_INTEGRATION.md`, but no file or folder `frontend/Angular/OPENAPI_INTEGRATION.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ATOMS_COMPLETE.md:229— docs/ATOMS_COMPLETE.md names Sass 2, but the manifest declares `sass` ^1.69.5. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate REDACTED:125— `context.Request.Headers.TryGetValue(HeaderNames.IfModifiedSince, out var modifiedSince) && DateTimeOffset.TryParse(modifiedSince, out var si…` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Endpoints/V1/Pizzas/PizzaImageEndpoint.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:119— `context.Request.Headers.TryGetValue(HeaderNames.IfNoneMatch, out var etags) && etags.Any(tag => string.Equals(tag.Trim(), image.eTag, String…` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Endpoints/V1/Pizzas/PizzaImageEndpoint.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/4.Utilities/Extensions/EnumExtensions.cs:12— `fi.GetCustomAttributes(typeof(DescriptionAttribute), false) is DescriptionAttribute[] attributes && attributes.Length != 0` appears character-identically in 5 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs, backend/.NET/2.CleanArchitecture/Domain/Extensions/EnumExtensions.cs, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Extensions/EnumExtensions.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/4.Utilities/Extensions/EnumExtensions.cs:22— `field.GetCustomAttributes(typeof(DescriptionAttribute), false).Length > 0 && string.Equals(((DescriptionAttribute)field.GetCustomAttributes(…` appears character-identically in 5 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/EnumExtensions.cs, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Common/Extensions/EnumExtensions.cs, backend/.NET/2.CleanArchitecture/Domain/Extensions/EnumExtensions.cs, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Extensions/EnumExtensions.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/Node/k6/load.js:16— `__ENV.BASE_URL || "http://localhost:3000"` appears character-identically in 2 files — backend/Node/k6/load.js, backend/Node/k6/smoke.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/Python/k6/load.js:16— `__ENV.BASE_URL || "http://localhost:8000"` appears character-identically in 2 files — backend/Python/k6/load.js, backend/Python/k6/smoke.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/Java/k6/load.js:16— `__ENV.BASE_URL || "http://localhost:8080"` appears character-identically in 2 files — backend/Java/k6/load.js, backend/Java/k6/smoke.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/comprehensive-all-endpoints.js:40— `__ENV.BASE_URL || 'http://localhost:5000'` appears character-identically in 32 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/comprehensive-all-endpoints.js, backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/health-check.js, backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js, backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/pizza-endpoints.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate frontend/Angular/src/app/shared/components/toast-banner/toast-banner.service.ts:153— `customMessage || 'An unexpected error occurred'` appears character-identically in 2 files — frontend/Angular/src/app/shared/components/toast-banner/toast-banner.service.ts, frontend/Angular/src/app/shared/services/toast.service.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js:195— `r.body.includes('[') || r.body.includes('data')` appears character-identically in 16 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js, backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/pizza-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/order-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/pizza-endpoints.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/pizza-endpoints.js:75— `r.body.includes('data') || r.body.includes('[')` appears character-identically in 8 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/pizza-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/pizza-endpoints.js, backend/.NET/2.CleanArchitecture/LoadTesting/k6/pizza-endpoints.js, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/pizza-endpoints.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/pizza-endpoints.js:110— `r.body.includes('id') || r.body.includes('Id')` appears character-identically in 8 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/pizza-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/pizza-endpoints.js, backend/.NET/2.CleanArchitecture/LoadTesting/k6/pizza-endpoints.js, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/pizza-endpoints.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js:72— `r.body.includes('id') || r.body.includes('Id') || r.body.includes('orderId')` appears character-identically in 8 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/order-endpoints.js, backend/.NET/2.CleanArchitecture/LoadTesting/k6/order-endpoints.js, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/order-endpoints.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js:73— `r.body.includes('status') || r.body.includes('Status')` appears character-identically in 8 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/order-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/order-endpoints.js, backend/.NET/2.CleanArchitecture/LoadTesting/k6/order-endpoints.js, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/order-endpoints.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/comprehensive-all-endpoints.js:188— `r.status === 200 || r.status === 204 || r.status === 404` appears character-identically in 16 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/comprehensive-all-endpoints.js, backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/pizza-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/comprehensive-all-endpoints.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/pizza-endpoints.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/health-check.js:55— `r.status === 200 || r.status === 404 || r.status === 400` appears character-identically in 8 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/LoadTesting/k6/health-check.js, backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/LoadTesting/k6/health-check.js, backend/.NET/2.CleanArchitecture/LoadTesting/k6/health-check.js, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/LoadTesting/k6/health-check.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate frontend/React/src/features/order/utils/orderHelpers.ts:99— `status === 'delivered' || status === 'cancelled'` appears character-identically in 2 files — frontend/React/src/features/order/utils/orderHelpers.ts, frontend/React/src/features/order/utils/orderStatus.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate backend/.NET/4.Utilities/Extensions/Extensions.cs:45— `pi.GetValue(myObject) is not string value || value.AsSpan().Trim().Length == 0` appears character-identically in 4 files — backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Common/Extensions/Extensions.cs, backend/.NET/2.CleanArchitecture/Domain/Extensions/Extensions.cs, backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Common/Extensions/Extensions.cs, backend/.NET/4.Utilities/Extensions/Extensions.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Deprecated: @humanwhocodes/config-array REDACTED:592— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:646— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:5765— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:6063— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:7356— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: superagent REDACTED:7805— superagent 8.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "Please upgrade to superagent v10.2.2+, see release notes at https://github.com/forwardemail/superagent/releases/tag/v10.2.2 - maintenance is supported by Forward Email @ https://forwardemail.net". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:8505— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:8843— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:11899— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:1063— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:1117— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:4632— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:4926— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:6934— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Fat interface: IPizzaClient (18 members) backend/.NET/2.CleanArchitecture/Api.Client/Api-Client-v1.cs:683— `IPizzaClient` declares 18 members under just 12 distinct name(s): `GetImageAsync`, `GetImage`, `GetImageAsync`, `GetAsync`, `Get`, `GetAsync`, `UpdateAsync`, `Update`, `UpdateAsync`, `DeleteAsync`, `Delete`, `DeleteAsync`, `SearchAsync`, `Search`, `SearchAsync`, `CreateAsync`, `Create`, `CreateAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: IClient (24 members) backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api.Client/Api-Client-v1.cs:27— `IClient` declares 24 members: `GetHcAsync`, `GetHc`, `GetHcAsync`, `Create_a_pizzaAsync`, `Create_a_pizza`, `Create_a_pizzaAsync`, `Update_pizzaAsync`, `Update_pizza`, `Update_pizzaAsync`, `GetPizzaImageAsync`, `GetPizzaImage`, `GetPizzaImageAsync`, `Search_for_pizzasAsync`, `Search_for_pizzas`, `Search_for_pizzasAsync`, `Complete_orderAsync`, `Complete_order`, `Complete_orderAsync`, `Create_orderAsync`, `Create_order`, `Create_orderAsync`, `Get_order_statusAsync`, `Get_order_status`, `Get_order_statusAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IPizzaClient (18 members) backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api.Client/Api-Client-v1.cs:683— `IPizzaClient` declares 18 members under just 12 distinct name(s): `GetImageAsync`, `GetImage`, `GetImageAsync`, `GetAsync`, `Get`, `GetAsync`, `UpdateAsync`, `Update`, `UpdateAsync`, `DeleteAsync`, `Delete`, `DeleteAsync`, `SearchAsync`, `Search`, `SearchAsync`, `CreateAsync`, `Create`, `CreateAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: IPizzaClient (18 members) backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api.Client/Api-Client-v1.cs:683— `IPizzaClient` declares 18 members under just 12 distinct name(s): `GetImageAsync`, `GetImage`, `GetImageAsync`, `GetAsync`, `Get`, `GetAsync`, `UpdateAsync`, `Update`, `UpdateAsync`, `DeleteAsync`, `Delete`, `DeleteAsync`, `SearchAsync`, `Search`, `SearchAsync`, `CreateAsync`, `Create`, `CreateAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: IPizzaClient (18 members) backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api.Client/Api-Client-v1.cs:683— `IPizzaClient` declares 18 members under just 12 distinct name(s): `GetImageAsync`, `GetImage`, `GetImageAsync`, `GetAsync`, `Get`, `GetAsync`, `UpdateAsync`, `Update`, `UpdateAsync`, `DeleteAsync`, `Delete`, `DeleteAsync`, `SearchAsync`, `Search`, `SearchAsync`, `CreateAsync`, `Create`, `CreateAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Silent fallback default on parse failure backend/.NET/2.CleanArchitecture/Api/Services/PizzaImageService.cs:36— `GetImage` falls back to `DefaultFileName` when `ImageFileNames.TryGetValue(pizzaId, out var mapped)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure backend/.NET/3.VerticalSliceArchitecture/2.Minimal/Api/Services/PizzaImageService.cs:36— `GetImage` falls back to `DefaultFileName` when `ImageFileNames.TryGetValue(pizzaId, out var mapped)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure backend/.NET/3.VerticalSliceArchitecture/1.Traditional/Api/Services/PizzaImageService.cs:36— `GetImage` falls back to `DefaultFileName` when `ImageFileNames.TryGetValue(pizzaId, out var mapped)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure backend/.NET/1.LayeredArchitecture/2. TemplateWithDataAccess/Api/Services/PizzaImageService.cs:36— `GetImage` falls back to `DefaultFileName` when `ImageFileNames.TryGetValue(pizzaId, out var mapped)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Services/PizzaImageService.cs:38— `GetImage` falls back to `DefaultFileName` when `ImageFileNames.TryGetValue(pizzaId, out var mapped)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Outdated: coverlet.collector — coverlet.collector 6.0.4 → 10.1.0 available (referenced by Test).
Outdated: coverlet.msbuild — coverlet.msbuild 6.0.4 → 10.1.0 available (referenced by Test).
D20 · ADR Quality· ADR has no Decision and Consequences section · ×2
ADR has no Decision and Consequences section docs/OPENAPI_GENERATION_SETUP_COMPLETE.md:1— docs/OPENAPI_GENERATION_SETUP_COMPLETE.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Decision and Consequences section docs/REVIEW_STATUS.md:1— docs/REVIEW_STATUS.md has no Decision and Consequences section (a heading such as `## Decision`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 62 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.
D21 · Naming Consistency· Inconsistent naming for the same database column concept ('Name'). Some fields use 'Table.Name' while others use 'Columns.Name'. While 'Table' and 'Columns' might refer to different scopes (table-level vs column-level metadata), the parallel structure suggests 'Columns.Name' is the standard for column definitions, making 'Table.Name' potentially confusing or inconsistent if they refer to the same underlying DB column name. · ×1
Inconsistent naming for the same database column concept ('Name'). Some fields use 'Table.Name' while others use 'Columns.Name'. While 'Table' and 'Columns' might refer to different scopes (table-level vs column-level metadata), the parallel structure suggests 'Columns.Name' is the standard for column definitions, making 'Table.Name' potentially confusing or inconsistent if they refer to the same underlying DB column name. — Standardize on 'Columns.Name' for all column definition fields, or clearly distinguish if 'Table.Name' refers to the table name itself (in which case it should be 'TableName'). (symbols: Field: public string Core.Database.EFMapping.PizzaMap.Table.Name, Field: public string Core.Database.EFMapping.PizzaMap.Columns.Name, Field: public string Features.Pizzas.V1.Mapping.PizzaMap.Columns.Name, Field: public string DataAccess.Mapping.PizzaMap.Columns.Name)
D21 · Naming Consistency· Inconsistent naming style for client methods. 'Search_for_pizzas' and 'Update_pizza' use snake_case with underscores, whereas the rest of the codebase (e.g., 'CreateAsync', 'DeleteAsync', 'GetAllPizzasQuery') uses PascalCase. This breaks the naming convention for public API methods. · ×1
Inconsistent naming style for client methods. 'Search_for_pizzas' and 'Update_pizza' use snake_case with underscores, whereas the rest of the codebase (e.g., 'CreateAsync', 'DeleteAsync', 'GetAllPizzasQuery') uses PascalCase. This breaks the naming convention for public API methods. — Rename to PascalCase: 'SearchPizzas', 'UpdatePizza', 'UpdatePizzaAsync'. (symbols: Method: public ResultOfIEnumerableOfPizzaModel Farris.API.Client.Template.Client.Search_for_pizzas(Farris.API.Client.Template.GetAllPizzasQuery), Method: public Task<ResultOfPizzaModel> Farris.API.Client.Template.Client.Update_pizza(Farris.API.Client.Template.UpdatePizzaCommand), Method: public Task<ResultOfPizzaModel> Farris.API.Client.Template.Client.Update_pizzaAsync(Farris.API.Client.Template.UpdatePizzaCommand))
D28 · Secrets (history)· Rotate the exposed credentials · ×1
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 12 ADR-shaped document(s) detected by content — `docs/ATOMS_COMPLETE.md`, `docs/COMPLETION_DASHBOARD.md`, `docs/OPENAPI_GENERATION_IMPLEMENTATION.md`, `docs/OPENAPI_GENERATION_SETUP_COMPLETE.md`, `docs/PHASE_2_COMPLETION.md`, `docs/REVIEW_STATUS.md`, `docs/SESSION_CONTINUATION_SUMMARY.md`, `docs/SESSION_FINAL_SUMMARY.md`, `docs/SESSION_SUMMARY_NOV_4.md`, `docs/TEMPLATE_REVIEW_SUMMARY.md`, `docs/TRANSFORMATION_COMPLETE.md`, `docs/TRANSFORMATION_SUMMARY.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
Inconsistent root namespaces — Only 10/48 projects share a common root namespace — the code's module identity is inconsistent.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 103/111 types (93%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P10 · Library API & versioning· No explicit versioning · ×1
No explicit versioning — No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.
Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `backend/Java`, `frontend/Angular`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Unused export 'OrderState' frontend/Angular/src/app/features/order/types/order.interface.ts:103— Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/Angular/src/app/features/order/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/Angular/src/app/features/order/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused private method 'clearError' · ×1
Unused private method 'clearError' frontend/Angular/src/app/features/order/services/cart.service.ts:186— Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used.
Security headers incomplete backend/.NET/2.CleanArchitecture/Api/StartupApp/App/SecurityApp.cs:9— Set: Permissions-Policy, X-Frame-Options. Missing: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.5 on this card.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 147/180 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.
Nullable reference types not enabled everywhere — 39/43 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.2 `!` suppressions per 1k syntax nodes — 5 suppression(s) across the 32094 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.
Mock framework: NSubstitute — Test references NSubstitute.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 63 file(s) — `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/Middleware/LoggingMiddleware.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Api/StartupApp/Services/CommonServices.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/DatabaseContext.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CompleteOrderCommand.cs`, `backend/.NET/1.LayeredArchitecture/1. CleanTemplate/Core/Orders/V1/Commands/CreateOrderCommand.cs`, … (+58 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a161ec-2d6c-771c-acd3-dcd37787351c · 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 — 25 field(s) across 1 category, 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: 124 · Warnings: 461 · Recommendations: 148 · Info: 325 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 04:43 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.