Public report of AlphaYu/adnc, 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, 01:01 UTC · Survey ID cd_cca979a687b94406ba9ee684c02d47e1
AlphaYu/adnc
Measured 22 October 2026, 00:52 UTC, at code version 58c015a
CAI scoreProvisionalDown 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 medium codebase: 27,536 lines of product code in 41 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Security and Compliance, 40
Findings by how serious they are
145 critical395 serious177 minor
4 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, 00:52 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 9 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0579: Duplicate 'global::System.Runtime.Versioning.TargetFrameworkAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyConfigurationAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyDescriptionAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute
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 ▸
92of 99 dimensions measured by tools. The other 7 are advisory notes from an AI model, which explain the code but don't count towards the score.
688of 717 findings point to an exact file and line, so you can open each one in the code. The other 29 concern the repository as a whole, such as missing documentation.
99dimensions across 8 lenses, read from 27,536 lines of product code in 41 projects.
AlphaYu/adnc scores 45 out of 100 and is rated Provisional, while five of its eight lenses score higher still: Performance at 60, Code Health at 68, Architecture at 82, Event-Driven at 100, and Maturity at 47. The score is provisional because the code didn't build, so the ratings may change once it does.
The score is lower than those five because the weakest lens counts most, and here that is Security and Compliance, which scores 40 and is rated Weak. The project has no recorded secrets history and no supply-chain provenance, so its Secrets (history) and Supply-chain Provenance & Signing dimensions score 0 out of 10, and until those reach 4, Security and Compliance can't be rated higher than Adequate. Resolving the 4 REDACTED finding, storing passwords with a salted KDF, and resolving the 42 High secret findings are the first actions, and if Security and Compliance rose to 70, the score would rise from 45 to about 50.
One hundred forty-five findings are critical: 42 high secrets in the history, 23 high IaC issues, 16 layer violations, 14 mutable action tags, 8 unpinned actions, 7 domain dependencies on infrastructure, 6 secrets in history, 5 leaked secrets, 5 analyzer severity none issues, 5 insecure binary formatter deserializations, 5 high CVEs, 4 interpolated secrets in run commands, 3 NoWarn in csproj files, 1 privileged service, and 1 password hashing without a KDF.
Watchdog couldn't measure Dependency Hygiene because it is not measured, IL Efficiency because the analyzer's build of the target did not succeed, and Runtime accessibility because compose up failed with exit 18 due to a forbidden response from the registry mirror, which is a limit of the sandbox. The product code is 27,536 lines, which would take an estimated 0.3 person-years, around €40,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 40 to 70, the lowest score rated Strong, the score would rise from 45 to about 50.
Code composition: what the lines of code are
Business logic 26%Supporting code 53%Tests 9%Generated by tools 12%
New since the last survey: 121 findings
These 121 critical or serious findings weren't in the previous survey, on 7 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 14 findings
These 14 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.
Dependency direction · Dependency-rule violation: Adnc.Demo.Whse.Domain (Domain) → Adnc.Infra.Helper (Infrastructure)
Dependency direction · Dependency-rule violation: Adnc.Demo.Whse.Domain (Domain) → Adnc.Infra.IdGenerater (Infrastructure)
Dependency direction · Dependency-rule violation: Adnc.Demo.Whse.Application (Application) → Adnc.Infra.Repository (Infrastructure)
Dependency direction · Dependency-rule violation: Adnc.Demo.Whse.Application (Application) → Adnc.Infra.Repository.EfCore.SqlServer (Infrastructure)
Dependency direction · Dependency-rule violation: Adnc.Demo.Ord.Domain (Domain) → Adnc.Infra.Helper (Infrastructure)
Dependency direction · Dependency-rule violation: Adnc.Demo.Ord.Domain (Domain) → Adnc.Infra.IdGenerater (Infrastructure)
Dependency direction · Dependency-rule violation: Adnc.Demo.Ord.Application (Application) → Adnc.Infra.Repository (Infrastructure)
Domain vs controller coverage · Low domain coverage
Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: WarehouseManager src/Demo/Whse/Domain/Services/WarehouseManager.cs
Rebuild cost: about €40,000 · Estimate
Cost to rebuild
€13,000 to €68,000, for 222 to 712 hours of work, about 0.3 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 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 27,536 lines of product code
Comment lines
The estimate prices 21,897 lines. Comment lines count towards the size of 27,536 lines but aren't priced as work.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`.
(A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Demo/Admin/Application/Validators/UserChangePwdDtoValidator.cs:20`.
Resolve the 42 High secret finding(s) in Secrets (history) — start with REDACTED (20), REDACTED (5), REDACTED (5).
Raises the score by about 3 points · Medium effort · Secrets (history)
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0579: Duplicate 'global::System.Runtime.Versioning.TargetFrameworkAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyConfigurationAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyDescriptionAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €40,000 to build again, about 0.3 person-years of work. Its weakest lens is Security and Compliance, at 40 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
One cause behind 14 Domain Modelling findings · Common cause
14 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (7 findings) · Rich vs anemic model (4 findings) · Strongly-typed ids (3 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
108 modules, with 81 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; 68 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.
Adnc.Infra.EventBus.Tracker uses Adnc.Infra.EventBus, so a change to Adnc.Infra.EventBus can break Adnc.Infra.EventBus.Tracker, while a change to Adnc.Infra.EventBus.Tracker can't break Adnc.Infra.EventBus.
Position
Below the diagonal: Adnc.Infra.EventBus.Tracker uses a module listed above it, which is the healthy direction.
Adnc.Infra.Helper uses Adnc.Infra.Helper.Internal.Encrypt, so a change to Adnc.Infra.Helper.Internal.Encrypt can break Adnc.Infra.Helper, while a change to Adnc.Infra.Helper can't break Adnc.Infra.Helper.Internal.Encrypt.
Position
Below the diagonal: Adnc.Infra.Helper uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis uses Adnc.Infra.Redis.Core.Serialization, so a change to Adnc.Infra.Redis.Core.Serialization can break Adnc.Infra.Redis, while a change to Adnc.Infra.Redis can't break Adnc.Infra.Redis.Core.Serialization.
Position
Below the diagonal: Adnc.Infra.Redis uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching uses Adnc.Infra.Redis.Caching.Configurations, so a change to Adnc.Infra.Redis.Caching.Configurations can break Adnc.Infra.Redis.Caching, while a change to Adnc.Infra.Redis.Caching can't break Adnc.Infra.Redis.Caching.Configurations.
Position
Below the diagonal: Adnc.Infra.Redis.Caching uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching uses Adnc.Infra.Redis.Caching.Core, so a change to Adnc.Infra.Redis.Caching.Core can break Adnc.Infra.Redis.Caching, while a change to Adnc.Infra.Redis.Caching can't break Adnc.Infra.Redis.Caching.Core.
Position
Below the diagonal: Adnc.Infra.Redis.Caching uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching uses Adnc.Infra.Redis.Core.Serialization, so a change to Adnc.Infra.Redis.Core.Serialization can break Adnc.Infra.Redis.Caching, while a change to Adnc.Infra.Redis.Caching can't break Adnc.Infra.Redis.Core.Serialization.
Position
Below the diagonal: Adnc.Infra.Redis.Caching uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Infra.Repository.EfCore, while a change to Adnc.Infra.Repository.EfCore can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore.Transaction uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Infra.Repository.EfCore.Transaction, while a change to Adnc.Infra.Repository.EfCore.Transaction can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore.Transaction uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.Interceptor.Castle uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Infra.Repository.Interceptor.Castle, while a change to Adnc.Infra.Repository.Interceptor.Castle can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Infra.Repository.Interceptor.Castle uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Registrar uses Adnc.Shared, so a change to Adnc.Shared can break Adnc.Shared.Application.Registrar, while a change to Adnc.Shared.Application.Registrar can't break Adnc.Shared.
Position
Below the diagonal: Adnc.Shared.Application.Registrar uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Services uses Adnc.Shared.Application.Contracts.ResultModels, so a change to Adnc.Shared.Application.Contracts.ResultModels can break Adnc.Shared.Application.Services, while a change to Adnc.Shared.Application.Services can't break Adnc.Shared.Application.Contracts.ResultModels.
Position
Below the diagonal: Adnc.Shared.Application.Services uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Services uses Adnc.Shared.Application.Mapper, so a change to Adnc.Shared.Application.Mapper can break Adnc.Shared.Application.Services, while a change to Adnc.Shared.Application.Services can't break Adnc.Shared.Application.Mapper.
Position
Below the diagonal: Adnc.Shared.Application.Services uses a module listed above it, which is the healthy direction.
Adnc.Shared.Repository.DapperEntities uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Shared.Repository.DapperEntities, while a change to Adnc.Shared.Repository.DapperEntities can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Shared.Repository.DapperEntities uses a module listed above it, which is the healthy direction.
Adnc.Shared.Repository.EfCoreEntities uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Shared.Repository.EfCoreEntities, while a change to Adnc.Shared.Repository.EfCoreEntities can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Shared.Repository.EfCoreEntities uses a module listed above it, which is the healthy direction.
Adnc.Shared.WebApi uses Adnc.Shared, so a change to Adnc.Shared can break Adnc.Shared.WebApi, while a change to Adnc.Shared.WebApi can't break Adnc.Shared.
Position
Below the diagonal: Adnc.Shared.WebApi uses a module listed above it, which is the healthy direction.
Adnc.Shared.WebApi.Authentication.Basic uses Adnc.Shared.Remote.Handlers.Token, so a change to Adnc.Shared.Remote.Handlers.Token can break Adnc.Shared.WebApi.Authentication.Basic, while a change to Adnc.Shared.WebApi.Authentication.Basic can't break Adnc.Shared.Remote.Handlers.Token.
Position
Below the diagonal: Adnc.Shared.WebApi.Authentication.Basic uses a module listed above it, which is the healthy direction.
Microsoft.Extensions.Configuration uses Adnc.Infra.Consul.Configuration, so a change to Adnc.Infra.Consul.Configuration can break Microsoft.Extensions.Configuration, while a change to Microsoft.Extensions.Configuration can't break Adnc.Infra.Consul.Configuration.
Position
Below the diagonal: Microsoft.Extensions.Configuration uses a module listed above it, which is the healthy direction.
Microsoft.Extensions.Configuration uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Microsoft.Extensions.Configuration, while a change to Microsoft.Extensions.Configuration can't break Adnc.Infra.Repository.
Position
Below the diagonal: Microsoft.Extensions.Configuration uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Core.BloomFilter uses Adnc.Infra.Redis.Configurations, so a change to Adnc.Infra.Redis.Configurations can break Adnc.Infra.Redis.Caching.Core.BloomFilter, while a change to Adnc.Infra.Redis.Caching.Core.BloomFilter can't break Adnc.Infra.Redis.Configurations.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Core.BloomFilter uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Core.BloomFilter uses Adnc.Infra.Redis, so a change to Adnc.Infra.Redis can break Adnc.Infra.Redis.Caching.Core.BloomFilter, while a change to Adnc.Infra.Redis.Caching.Core.BloomFilter can't break Adnc.Infra.Redis.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Core.BloomFilter uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Core.Interceptor.Castle uses Adnc.Infra.Redis.Caching, so a change to Adnc.Infra.Redis.Caching can break Adnc.Infra.Redis.Caching.Core.Interceptor.Castle, while a change to Adnc.Infra.Redis.Caching.Core.Interceptor.Castle can't break Adnc.Infra.Redis.Caching.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Core.Interceptor.Castle uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Providers.StackExchange uses Adnc.Infra.Redis.Configurations, so a change to Adnc.Infra.Redis.Configurations can break Adnc.Infra.Redis.Providers.StackExchange, while a change to Adnc.Infra.Redis.Providers.StackExchange can't break Adnc.Infra.Redis.Configurations.
Position
Below the diagonal: Adnc.Infra.Redis.Providers.StackExchange uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Providers.StackExchange uses Adnc.Infra.Redis.Core.Serialization, so a change to Adnc.Infra.Redis.Core.Serialization can break Adnc.Infra.Redis.Providers.StackExchange, while a change to Adnc.Infra.Redis.Providers.StackExchange can't break Adnc.Infra.Redis.Core.Serialization.
Position
Below the diagonal: Adnc.Infra.Redis.Providers.StackExchange uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Providers.StackExchange uses Adnc.Infra.Redis, so a change to Adnc.Infra.Redis can break Adnc.Infra.Redis.Providers.StackExchange, while a change to Adnc.Infra.Redis.Providers.StackExchange can't break Adnc.Infra.Redis.
Position
Below the diagonal: Adnc.Infra.Redis.Providers.StackExchange uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore.MongoDB uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Infra.Repository.EfCore.MongoDB, while a change to Adnc.Infra.Repository.EfCore.MongoDB can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore.MongoDB uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore.MongoDB uses Adnc.Infra.Repository.EfCore, so a change to Adnc.Infra.Repository.EfCore can break Adnc.Infra.Repository.EfCore.MongoDB, while a change to Adnc.Infra.Repository.EfCore.MongoDB can't break Adnc.Infra.Repository.EfCore.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore.MongoDB uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore.MySql uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Infra.Repository.EfCore.MySql, while a change to Adnc.Infra.Repository.EfCore.MySql can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore.MySql uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore.MySql uses Adnc.Infra.Repository.EfCore, so a change to Adnc.Infra.Repository.EfCore can break Adnc.Infra.Repository.EfCore.MySql, while a change to Adnc.Infra.Repository.EfCore.MySql can't break Adnc.Infra.Repository.EfCore.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore.MySql uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore.SqlServer uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Infra.Repository.EfCore.SqlServer, while a change to Adnc.Infra.Repository.EfCore.SqlServer can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore.SqlServer uses a module listed above it, which is the healthy direction.
Adnc.Infra.Repository.EfCore.SqlServer uses Adnc.Infra.Repository.EfCore, so a change to Adnc.Infra.Repository.EfCore can break Adnc.Infra.Repository.EfCore.SqlServer, while a change to Adnc.Infra.Repository.EfCore.SqlServer can't break Adnc.Infra.Repository.EfCore.
Position
Below the diagonal: Adnc.Infra.Repository.EfCore.SqlServer uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Interceptors uses Adnc.Shared, so a change to Adnc.Shared can break Adnc.Shared.Application.Interceptors, while a change to Adnc.Shared.Application.Interceptors can't break Adnc.Shared.
Position
Below the diagonal: Adnc.Shared.Application.Interceptors uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Interceptors uses Adnc.Shared.Repository.DapperEntities, so a change to Adnc.Shared.Repository.DapperEntities can break Adnc.Shared.Application.Interceptors, while a change to Adnc.Shared.Application.Interceptors can't break Adnc.Shared.Repository.DapperEntities.
Position
Below the diagonal: Adnc.Shared.Application.Interceptors uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Services.Trackers uses Adnc.Infra.EventBus, so a change to Adnc.Infra.EventBus can break Adnc.Shared.Application.Services.Trackers, while a change to Adnc.Shared.Application.Services.Trackers can't break Adnc.Infra.EventBus.
Position
Below the diagonal: Adnc.Shared.Application.Services.Trackers uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Services.Trackers uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Shared.Application.Services.Trackers, while a change to Adnc.Shared.Application.Services.Trackers can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Shared.Application.Services.Trackers uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Services.Trackers uses Adnc.Infra.EventBus.Tracker, so a change to Adnc.Infra.EventBus.Tracker can break Adnc.Shared.Application.Services.Trackers, while a change to Adnc.Shared.Application.Services.Trackers can't break Adnc.Infra.EventBus.Tracker.
Position
Below the diagonal: Adnc.Shared.Application.Services.Trackers uses a module listed above it, which is the healthy direction.
Adnc.Shared.Application.Services.Trackers uses Adnc.Shared.Repository.EfCoreEntities, so a change to Adnc.Shared.Repository.EfCoreEntities can break Adnc.Shared.Application.Services.Trackers, while a change to Adnc.Shared.Application.Services.Trackers can't break Adnc.Shared.Repository.EfCoreEntities.
Position
Below the diagonal: Adnc.Shared.Application.Services.Trackers uses a module listed above it, which is the healthy direction.
Adnc.Shared.Domain.Entities uses Adnc.Infra.EventBus, so a change to Adnc.Infra.EventBus can break Adnc.Shared.Domain.Entities, while a change to Adnc.Shared.Domain.Entities can't break Adnc.Infra.EventBus.
Position
Below the diagonal: Adnc.Shared.Domain.Entities uses a module listed above it, which is the healthy direction.
Adnc.Shared.Domain.Entities uses Adnc.Infra.Repository, so a change to Adnc.Infra.Repository can break Adnc.Shared.Domain.Entities, while a change to Adnc.Shared.Domain.Entities can't break Adnc.Infra.Repository.
Position
Below the diagonal: Adnc.Shared.Domain.Entities uses a module listed above it, which is the healthy direction.
Adnc.Shared.Domain.Entities uses Adnc.Infra.Repository.EfCore, so a change to Adnc.Infra.Repository.EfCore can break Adnc.Shared.Domain.Entities, while a change to Adnc.Shared.Domain.Entities can't break Adnc.Infra.Repository.EfCore.
Position
Below the diagonal: Adnc.Shared.Domain.Entities uses a module listed above it, which is the healthy direction.
Adnc.Shared.WebApi.Authentication.Processors uses Adnc.Shared.Remote.Http.Services, so a change to Adnc.Shared.Remote.Http.Services can break Adnc.Shared.WebApi.Authentication.Processors, while a change to Adnc.Shared.WebApi.Authentication.Processors can't break Adnc.Shared.Remote.Http.Services.
Position
Below the diagonal: Adnc.Shared.WebApi.Authentication.Processors uses a module listed above it, which is the healthy direction.
Adnc.Shared.WebApi.Authentication.Processors uses Adnc.Infra.Redis.Caching, so a change to Adnc.Infra.Redis.Caching can break Adnc.Shared.WebApi.Authentication.Processors, while a change to Adnc.Shared.WebApi.Authentication.Processors can't break Adnc.Infra.Redis.Caching.
Position
Below the diagonal: Adnc.Shared.WebApi.Authentication.Processors uses a module listed above it, which is the healthy direction.
Adnc.Shared.WebApi.Authorization.Handlers uses Adnc.Shared.Remote.Http.Services, so a change to Adnc.Shared.Remote.Http.Services can break Adnc.Shared.WebApi.Authorization.Handlers, while a change to Adnc.Shared.WebApi.Authorization.Handlers can't break Adnc.Shared.Remote.Http.Services.
Position
Below the diagonal: Adnc.Shared.WebApi.Authorization.Handlers uses a module listed above it, which is the healthy direction.
Adnc.Shared.WebApi.Authorization.Handlers uses Adnc.Infra.Redis.Caching, so a change to Adnc.Infra.Redis.Caching can break Adnc.Shared.WebApi.Authorization.Handlers, while a change to Adnc.Shared.WebApi.Authorization.Handlers can't break Adnc.Infra.Redis.Caching.
Position
Below the diagonal: Adnc.Shared.WebApi.Authorization.Handlers uses a module listed above it, which is the healthy direction.
Microsoft.Extensions.DependencyInjection.Extensions uses Adnc.Shared.WebApi.Authentication.Basic, so a change to Adnc.Shared.WebApi.Authentication.Basic can break Microsoft.Extensions.DependencyInjection.Extensions, while a change to Microsoft.Extensions.DependencyInjection.Extensions can't break Adnc.Shared.WebApi.Authentication.Basic.
Position
Below the diagonal: Microsoft.Extensions.DependencyInjection.Extensions uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Provider uses Adnc.Infra.Redis.Caching.Configurations, so a change to Adnc.Infra.Redis.Caching.Configurations can break Adnc.Infra.Redis.Caching.Provider, while a change to Adnc.Infra.Redis.Caching.Provider can't break Adnc.Infra.Redis.Caching.Configurations.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Provider uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Provider uses Adnc.Infra.Redis.Caching.Core, so a change to Adnc.Infra.Redis.Caching.Core can break Adnc.Infra.Redis.Caching.Provider, while a change to Adnc.Infra.Redis.Caching.Provider can't break Adnc.Infra.Redis.Caching.Core.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Provider uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Provider uses Adnc.Infra.Redis.Configurations, so a change to Adnc.Infra.Redis.Configurations can break Adnc.Infra.Redis.Caching.Provider, while a change to Adnc.Infra.Redis.Caching.Provider can't break Adnc.Infra.Redis.Configurations.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Provider uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Provider uses Adnc.Infra.Redis.Core.Serialization, so a change to Adnc.Infra.Redis.Core.Serialization can break Adnc.Infra.Redis.Caching.Provider, while a change to Adnc.Infra.Redis.Caching.Provider can't break Adnc.Infra.Redis.Core.Serialization.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Provider uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Provider uses Adnc.Infra.Redis.Caching, so a change to Adnc.Infra.Redis.Caching can break Adnc.Infra.Redis.Caching.Provider, while a change to Adnc.Infra.Redis.Caching.Provider can't break Adnc.Infra.Redis.Caching.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Provider uses a module listed above it, which is the healthy direction.
Adnc.Infra.Redis.Caching.Provider uses Adnc.Infra.Redis.Providers.StackExchange, so a change to Adnc.Infra.Redis.Providers.StackExchange can break Adnc.Infra.Redis.Caching.Provider, while a change to Adnc.Infra.Redis.Caching.Provider can't break Adnc.Infra.Redis.Providers.StackExchange.
Position
Below the diagonal: Adnc.Infra.Redis.Caching.Provider uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 68% · Adequate · gated by D18 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
69
High / Critical
A07:2025 — Authentication Failures
54
High / Critical
A02:2025 — Security Misconfiguration
25
High / Critical
A03:2025 — Software Supply Chain Failures
18
High / Critical
Roadmap
Immediately secure the web application by implementing proper password hashing with a salted KDF and constant-time comparison, beginning in the user password change validator. Simultaneously, remove all hardcoded secrets from configuration files and resolve high-severity issues in the Docker Compose infrastructure to eliminate immediate exposure risks. Finally, strengthen data protection by centralizing key management in a vault and encrypting sensitive columns, while refactoring the codebase to enforce strict repository boundaries per aggregate root.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Demo/Admin/Application/Validators/UserChangePwdDtoValidator.cs:20`.
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 — 145
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 — 395
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 — 177
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 4
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. 92 of 99 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 7 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 — 99 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, 688 of 717 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.
D9 Test Distribution — 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. 111 test method(s) were found on disk (co-located in feature projects, or outside the analyzed solution) rather than in dedicated test projects, so the unit/integration/E2E pyramid can't be classified — they're counted as one undifferentiated suite. You can widen what we reach: moving the tests into dedicated test projects inside the analyzed solution would let the unit/integration/BDD/E2E split be classified — but the counting gap is ours, so nothing is deducted either way.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (11 contributor(s) across 1882 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 10 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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. `REDACTED`, `REDACTED`, `src/Demo/Admin/Api/Controllers/DictDataController.cs`, `REDACTED`, `REDACTED`, … (+125 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.
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) — consul_client_1 Error context canceled nginx Error context canceled redis Error context canceled consul_server_1 Error context canceled grafana Error context canceled consul_server_2 Error context canceled consul_server_3 Error context canceled mariadb Error context canceled promtail Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: redis Pulling grafana Pulling mariadb Error Get "https://registry-1.docker.io/v2/": Forbidden loki Error context canceled rabbitmq Error context canceled consul_server_1 Error context canceled nginx Error context canceled redis Error context canceled promtail Error context canceled grafana Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 68 further occurrence(s) are not listed individually; the score already reflects all 108.
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. 109 further occurrence(s) are not listed individually; the score already reflects all 149.
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 206 further occurrence(s) are not listed individually; the score already reflects all 246.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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 (7): D19, D20, D21, D22, D24, D25, 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 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with RSAKeyExtensions.FromLvccXmlString (cyclomatic 20). — Refactoring it lifts Cyclomatic Complexity from 9.6 to about 10.0/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with RSAKeyExtensions.FromLvccXmlString (cognitive 40). — Refactoring it lifts Cognitive Complexity from 8.4 to about 8.7/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.3 / 10Stronggated by 4 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 4 TooManyMethods finding(s) in God Classes — start with DefaultRedisProvider.List.cs, EncryptProvider.Rsa.cs, AbstracCacheProvider.cs. — One of this dimension's main actionable groups (4 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
63 duplicated block group(s) detected. A further 9 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 13 of the 72 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:18
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with ExpressionLogicalOperatorsExtension .cs, EncryptProvider.Rsa.cs, CacheTracingDiagnosticProcessor.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with EncryptProvider.Rsa.cs (3), IDatabaseExtension.cs, MySQLUnitOfWork.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with EncryptProivder.Aes.cs, DefaultCachingProvider.Async.cs, DefaultRedisProvider.Hash.cs. — One of this dimension's main actionable groups (5 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.6 / 10Adequategated by 16 critical findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
Off the main sequence: Adnc.Infra.Coresrc/Infrastructures/Core/Adnc.Infra.Core.csproj:1
Off the main sequence: Adnc.Sharedsrc/ServiceShared/Shared/Adnc.Shared.csproj:1
What to do
Resolve the 16 Layer violation finding(s) in Coupling — start with Adnc.Shared.Application.csproj (6), Adnc.Shared.Domain.csproj (3), Adnc.Demo.Ord.Domain.csproj (2). — One of this dimension's main actionable groups (16 issue-level).
Resolve the 1 Unstable project Adnc.Infra.Repository.EfCore.MongoDB finding(s) in Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Off the main sequence finding(s) in Coupling — start with Adnc.Infra.Core.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
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.
No mechanizable ADR was identified, so enforcement is not measured. Cycles found: 0.
What to do
Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D8 · Code Coverage7.2 / 10Strong✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No test project references Adnc.Shared.WebApiREDACTED
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 54 Low coverage finding(s) in Code Coverage — start with ServiceCollectionExtension.cs, HostExtension.cs, ConfigurationBuilderExtension.cs. — One of this dimension's main actionable groups (54 warning-level).
Resolve the 2 CRAP 240 finding(s) in Code Coverage — start with DataTimeExtension.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 CRAP 110 finding(s) in Code Coverage — start with JsonConfigurationFileParser.cs, DataTimeExtension.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test 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.
111 test methods: 111 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 1 serious finding✓ 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, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 111 tests.
No assertions: TestSpeedtest/Unittest.Redis/TestCases/IdGeneraterTests.cs:46
What to do
Resolve the 1 No assertions finding(s) in Test Quality — start with IdGeneraterTests.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 174 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 94 direct `PackageReference`(s), and 132 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (2), EasyCaching.Redis.csproj. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 52 CommentedOutCode finding(s) in Explicit Debt — start with EncryptExtensions.cs (10), CacheDelegatingHandler.cs (6), REDACTED (4). — One of this dimension's main actionable groups (52 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape3.0 / 10Weak✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
40 projects, 611 source files, 27110 hand-written lines of code (27110 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 3355 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 131 inter-project edges (build failed).
Build failed
Thin analysable surface across projects: Adnc.Demo.Whse.Migrations · ×2src/Demo/Whse/Migrations/Adnc.Demo.Whse.Migrations.csproj
What to do
Resolve the 2 Thin analysable surface across projects finding(s) in Solution Shape — start with Adnc.Demo.Whse.Migrations.csproj, Adnc.Demo.Ord.Migrations.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
ADNC's documentation is comprehensive and well-structured across READMEs, architecture/ADR documents, and XML coverage: a single root README covering overview, installation, usage, contributing, and license; the docs directory itself (README.md) provides focused per-directory documentation for subdirectories; and an extensive architecture section with ADRs covers design principles, distributed capabilities, observability, and migration guidance. The quality is high due to its breadth of topics and clear ordering. The Docker deployment guide is excellent at its one focused purpose: describing how to quickly deploy a new ADNC project using Docker Compose and custom networks, with clear steps for directory structure, network setup, SDK install, code upload, script execution, and verification. It is well written and complete within the clip boundary (sections 1-9 plus an outline of 10 unshown ones). The README files are strong but not shown in this document; the guide alone does not cover the project's overview, installation for non-Docker tiers, or contribution guidance.
Improve Documentation Quality — currently 8.9/10. — ADNC's documentation is comprehensive and well-structured across READMEs, architecture/ADR documents, and XML coverage: a single root README covering overview, installation, usage, contributing, and license; the docs directory itself (README.md) provides focused per-directory documentation for subdirectories; and an extensive architecture section with ADRs covers design principles, distributed capabilities, observability, and migration guidance. The quality is high due to its breadth of topics and clear ordering. The Docker deployment guide is excellent at its one focused purpose: describing how to quickly deploy a new ADNC project using Docker Compose and custom networks, with clear steps for directory structure, network setup, SDK install, code upload, script execution, and verification. It is well written and complete within the clip boundary (sections 1-9 plus an outline of 10 unshown ones). The README files are strong but not shown in this document; the guide alone does not cover the project's overview, installation for non-Docker tiers, or contribution guidance.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR QualityWeak◐ 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.
Evaluated 6 ADR(s) individually; mean quality 4.3/10 (frequently incomplete). 5 flagged with a specific gap.
No context/problem and no consequences/trade-offs; only the title 'ADR-002-outbox-pattern' is presentdocs/architecture/adr/ADR-002-outbox-pattern.md
No context/problem and no consequences; the title is informative but the body is a single decision with no rationale or trade-offsdocs/architecture/adr/ADR-003-no-distributed-transaction-coordinator.md
No context/problem and no consequences/trade-offs; only the title "ADR-004-event-bus-abstraction" is informativedocs/architecture/adr/ADR-004-event-bus-abstraction.md
No context/problem and no consequences/trade-offs; only the title 'ADR-005-redis-as-distributed-foundation' is informativedocs/architecture/adr/ADR-005-redis-as-distributed-foundation.md
No context/problem and no consequences/trade-offs; only the title 'opentelemetry-observability' is informativedocs/architecture/adr/ADR-006-opentelemetry-observability.md
What to do
Resolve the 1 No context/problem and no consequences/trade-offs; only the title… finding(s) in ADR Quality — start with ADR-002-outbox-pattern.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No context/problem and no consequences; the title is informative but the… finding(s) in ADR Quality — start with ADR-003-no-distributed-transaction-coordinator.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No context/problem and no consequences/trade-offs; only the title… finding(s) in ADR Quality — start with ADR-004-event-bus-abstraction.md. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D21 · Naming ConsistencyWeak◐ Sampled · 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.
9 naming inconsistencies across 200 sampled symbols.
Inconsistent spelling of the word 'Generator'. The codebase uses 'Generater' (missing the second 'e') in several symbols related to ID generation and hash consistency, while the standard spelling is 'Generator'.
Typo in the class name 'EncryptProivder'. The word 'Provider' is misspelled as 'Proivder' across all methods in this class.
Typo in the class name 'DocumenationExtension'. The word 'Documentation' is misspelled as 'Documenation' (missing 't').
Inconsistent spelling of 'Cache'. The class 'CahceConsts' misspells 'Cache' as 'Cahce', while other caching-related classes use the correct spelling 'Cache'.
Inconsistent naming for constant holder classes. Some use 'Consts' (plural) while others use 'ConstValue' (singular) or 'Consts' in different contexts. Specifically, 'RouteConsts' and 'PermissionConsts' use the plural form, while 'CachingConstValue' uses a singular noun phrase. While not a strict typo, the pattern is inconsistent across similar utility classes.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Inconsistent spelling of the word 'Generator'. The codebase uses… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Typo in the class name 'EncryptProivder'. The word 'Provider' is… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Typo in the class name 'DocumenationExtension'. The word 'Documentation'… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStrong◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
Inconsistent search parameter types for paged queries. Some services (Dict, Role, SysConfig) use a generic `SearchPagedDto`, while others (DictData, User) use domain-specific search DTOs. This forces consumers to know which specific search DTO to instantiate for each entity, rather than using a unified search interface.
Inconsistent naming and parameter structure for tree retrieval. `GetTreelistAsync` vs `GetTreeListAsync` (naming convention inconsistency: 'Treelist' vs 'Tree List'). Furthermore, Menu accepts only keywords, while Organization accepts name and status, lacking a unified filter interface.
Inconsistent naming for menu-related retrieval operations. `GetMenusForRouterAsync` implies a specific use case (router generation), while `GetMenuOptionsAsync` implies a UI dropdown use case. While distinct, the naming convention is inconsistent (`ForRouter` vs `Options`).
What to do
Resolve the 1 Inconsistent search parameter types for paged queries. Some services… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent naming and parameter structure for tree retrieval.… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent naming for menu-related retrieval operations.… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
4 domain type(s) cross context boundaries across 4 contexts.
Cross-context type TrackerKind (Infrastructures → ServiceShared) · ×4src/ServiceShared/Application/Services/Trackers/DbMessageTrackerService.cs:10
What to do
Resolve the 4 Cross-context type TrackerKind (Infrastructures → ServiceShared) finding(s) in Boundary Type-Coupling — start with DbMessageTrackerService.cs, MessageTrackerFactory.cs, NullMessageTrackerService.cs. — One of this dimension's main actionable groups (4 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: 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: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
95 % of calls cross a namespace and 7 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged 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.
48 finding(s): 0 critical, 48 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 42 High secret finding(s) in Secrets (history) — start with REDACTED (20), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (42 issue-level).
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 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).
69 finding(s): 0 critical, 32 high, 37 medium, 0 low. 14 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 131 file(s) — `REDACTED` (line 10), `REDACTED` (line 10), `src/Demo/Admin/Api/Controllers/DictDataController.cs` (line 10), `REDACTED` (line 10), `REDACTED` (line 10), … (+126 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 129 of those file(s) — `REDACTED`, `REDACTED`, `src/Demo/Admin/Api/Controllers/DictDataController.cs`, `REDACTED`, `REDACTED`, … (+124 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 1 of those file(s) — `src/ServiceShared/Application/Extensions/DependencyRegistrarExtension.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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
No action in Static Analysis (SAST) — all 14 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 (14 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.
Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 23 High IaC finding(s) in IaC & Container Security — start with REDACTED (23). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-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 83 of the 326 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.
Resolve the 6 Change coupling finding(s) in Change Coupling — start with BaseRabbitMqConsumer.cs, PermissionRemoteHandler.cs, HostExtension.cs. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. 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.
`IEventPublisher` declares 16 members under just 4 distinct name(s): `PublishAsync`, `PublishAsync`, `Publish`, `Publish`, `PublishDelayAsync`, `PublishDelayAsync`, `PublishDelay`, `PublishDelay`, `PublishAsync`, `PublishAsync`, `Publish`, `Publish`, `PublishDelayAsync`, `PublishDelayAsync`, `PublishDelay`, `PublishDelay`. 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 16 separate responsibilities: a caller binds to 4 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 16 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. — src/Infrastructures/EventBus/IEventPublisher.cs:3
`IAdoQuerierRepository` declares 22 members under just 5 distinct name(s): `QueryAsync`, `QueryAsync`, `QueryFirstAsync`, `QueryFirstOrDefaultAsync`, `QuerySingleAsync`, `QuerySingleOrDefaultAsync`, `QueryFirstAsync`, `QueryFirstOrDefaultAsync`, `QuerySingleAsync`, `QuerySingleOrDefaultAsync`, `QueryAsync`, `QueryFirstAsync`, `QueryFirstOrDefaultAsync`, `QuerySingleAsync`, `QuerySingleOrDefaultAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`. 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 22 separate responsibilities: a caller binds to 5 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 22 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. — src/Infrastructures/Repository/Interface/IAdoQuerierRepository.cs:3
`IRedisProvider` declares 134 members: `Serializer`, `KeyDel`, `KeyDelAsync`, `KeyExpire`, `KeyExpireAsync`, `KeyExistsAsync`, `KeyExists`, `TTL`, `TTLAsync`, `IncrBy`, `IncrByAsync`, `IncrByFloat`, `IncrByFloatAsync`, `StringSet`, `StringSetAsync`, `StringGet`, `StringGetAsync`, `StringLen`, `StringLenAsync`, `StringSetRange`, `StringSetRangeAsync`, `StringGetRange`, `StringGetRangeAsync`, `HMSet`, `HSet`, `HExists`, `HDel`, `HGet`, `HGetAll`, `HIncrBy`, `HKeys`, `HLen`, `HVals`, `HMGet`, `HMSetAsync`, `HSetAsync`, `HExistsAsync`, `HDelAsync`, `HGetAsync`, `HGetAllAsync`, and 94 more. 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 134 declarations carry 127 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 127 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. — src/Infrastructures/Redis/IRedisProvider.cs:12
`ICacheProvider` declares 23 members: `Name`, `CacheOptions`, `Serializer`, `Set`, `SetAsync`, `Get`, `GetAsync`, `Remove`, `RemoveAsync`, `ExistsAsync`, `Exists`, `TrySet`, `TrySetAsync`, `SetAll`, `SetAllAsync`, `RemoveAll`, `RemoveAllAsync`, `Get`, `GetAsync`, `RemoveByPrefix`, `RemoveByPrefixAsync`, `GetAsync`, `KeyExpireAsync`. 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 23 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 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. — src/Infrastructures/Redis.Caching/ICacheProvider.cs:7
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
C3 · Audit Trail7.5 / 10Strong✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
Do you agree with this assessment?
C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`LoginLog.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that. — src/ServiceShared/Repository/DapperEntities/LoginLog.cs:16
`OperationLog.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that. — src/ServiceShared/Repository/DapperEntities/OperationLog.cs:41
`EventTracker.EventId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that. — src/ServiceShared/Repository/EfCoreEntities/EventTracker.cs:12
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`LoginLog` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/ServiceShared/Repository/DapperEntities/LoginLog.cs:6
`OperationLog` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/ServiceShared/Repository/DapperEntities/OperationLog.cs:6
`EventTracker` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/ServiceShared/Repository/EfCoreEntities/EventTracker.cs:10
`AggregateRootWithBasicAuditInfo` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/ServiceShared/Domain/Entities/AggregateRootWithBasicAuditInfo.cs:3
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
`EfBasicAuditEntity` exposes publicly writable state (CreateBy, CreateTime). — src/Infrastructures/Repository/Entities/EfEnities/EfBasicAuditEntity.cs:3
`LoginLog` exposes publicly writable state (Device, Message, Succeed, StatusCode, UserId, Account, and 4 more). — src/ServiceShared/Repository/DapperEntities/LoginLog.cs:6
`OperationLog` exposes publicly writable state (ClassName, LogName, LogType, Message, Method, Succeed, and 6 more). — src/ServiceShared/Repository/DapperEntities/OperationLog.cs:6
`EventTracker` exposes publicly writable state (EventId, TrackerName). — src/ServiceShared/Repository/EfCoreEntities/EventTracker.cs:10
`AggregateRoot` exposes publicly writable state (RowVersion). — src/ServiceShared/Domain/Entities/AggregateRoot.cs:3
`AggregateRootWithBasicAuditInfo` exposes publicly writable state (CreateBy, CreateTime). — src/ServiceShared/Domain/Entities/AggregateRootWithBasicAuditInfo.cs:3
What to do
Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
`EntityInfo` (domain layer) names `ModelBuilder` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. (×2) — src/Demo/Ord/Domain/EntityConfig/EntityInfo.cs:7, src/Demo/Whse/Domain/EntityConfig/EntityInfo.cs:7
`OrderConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Demo/Ord/Domain/EntityConfig/OrderConfig.cs:5
`OrderItemConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Demo/Ord/Domain/EntityConfig/OrderItemConfig.cs:5
`ProductConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Demo/Whse/Domain/EntityConfig/ProductConfig.cs:7
`WarehouseConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it. — src/Demo/Whse/Domain/EntityConfig/WarehouseConfig.cs:7
`WarehouseManager` (domain layer) names `EntityFrameworkQueryableExtensions` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — src/Demo/Whse/Domain/Services/WarehouseManager.cs:39
What to do
Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.
Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.
Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.
`IEfBaseRepository` returns `IQueryable` from `Where`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — src/Infrastructures/Repository/Interface/IEfBaseRepository.cs:7
`IEfRepository` returns `IQueryable` from `GetAll`, `GetAll`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — src/Infrastructures/Repository/Interface/IEfRepository.cs:10
`IMongoDbRepository` returns `IQueryable` from `Where`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked. — src/Infrastructures/Repository/Interface/IMongoDbRepository.cs:3
What to do
Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
Do you agree with this assessment?
ED3 · Event naming7.0 / 10Strong✓ Tool-verified
Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).
Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.
`EventEntity` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — src/Infrastructures/EventBus/BaseEvent.cs:37
What to do
Name events in the past tense — they record facts that already happened.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:228, src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:255
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. (×2) — src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:14, src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:155
`LPushXAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:228
`RPushXAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:255
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×35) — src/Gateways/Ocelot/ThreadPoolSettings.cs:17, src/Infrastructures/EventBus/RabbitMq/RabbitMqProducer.cs:60, src/Infrastructures/EventBus/RabbitMq/RabbitMqProducer.cs:62, …
8 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/Infrastructures/EventBus/RabbitMq/RabbitMqProducer.cs:11
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 41 of 41 project(s) that lack one — worth up to 2 pts.
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.
docs/README.md links to `wiki/en/01-adnc-intro`, but `docs/wiki/en/01-adnc-intro` 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. — docs/README.md:9
docs/README.md links to `wiki/en/02-quickstart`, but `docs/wiki/en/02-quickstart` 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. — docs/README.md:10
docs/README.md links to `wiki/en/03-quickly-docker-deploy`, but `docs/wiki/en/03-quickly-docker-deploy` 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. — docs/README.md:11
docs/README.md links to `wiki/en/04-appsettings`, but `docs/wiki/en/04-appsettings` 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. — docs/README.md:15
docs/README.md links to `wiki/en/05-feature-dev-guide`, but `docs/wiki/en/05-feature-dev-guide` 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. — docs/README.md:16
docs/README.md links to `wiki/en/06-repository-dev-guide`, but `docs/wiki/en/06-repository-dev-guide` 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. — docs/README.md:17
docs/README.md links to `wiki/en/07-service-dev-guide`, but `docs/wiki/en/07-service-dev-guide` 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. — docs/README.md:18
docs/README.md links to `wiki/en/08-api-dev-guide`, but `docs/wiki/en/08-api-dev-guide` 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. — docs/README.md:19
docs/README.md links to `wiki/en/09-claims-based-authentication`, but `docs/wiki/en/09-claims-based-authentication` 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. — docs/README.md:20
docs/README.md links to `wiki/en/10-efcore-pemelo-curd`, but `docs/wiki/en/10-efcore-pemelo-curd` 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. — docs/README.md:24
docs/README.md links to `wiki/en/11-efcore-pemelo-codefirst`, but `docs/wiki/en/11-efcore-pemelo-codefirst` 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. — docs/README.md:25
docs/README.md links to `wiki/en/12-efcore-pemelo-sqlserver`, but `docs/wiki/en/12-efcore-pemelo-sqlserver` 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. — docs/README.md:26
docs/README.md links to `wiki/en/13-efcore-pemolo-unitofwork`, but `docs/wiki/en/13-efcore-pemolo-unitofwork` 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. — docs/README.md:27
docs/README.md links to `wiki/en/14-efcore-pemelo-sql`, but `docs/wiki/en/14-efcore-pemelo-sql` 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. — docs/README.md:28
docs/README.md links to `wiki/en/15-maxsale-readwritesplit`, but `docs/wiki/en/15-maxsale-readwritesplit` 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. — docs/README.md:29
docs/README.md links to `wiki/en/16-snowflake-max_value-wokerid`, but `docs/wiki/en/16-snowflake-max_value-wokerid` 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. — docs/README.md:33
docs/README.md links to `wiki/en/17-cache-redis-distributedlock-bloomfilter`, but `docs/wiki/en/17-cache-redis-distributedlock-bloomfilter` 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. — docs/README.md:34
docs/README.md links to `wiki/en/18-service-http-call`, but `docs/wiki/en/18-service-http-call` 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. — docs/README.md:35
docs/README.md links to `wiki/en/19-service-grpc-call`, but `docs/wiki/en/19-service-grpc-call` 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. — docs/README.md:36
docs/README.md links to `wiki/en/20-service-event-call`, but `docs/wiki/en/20-service-event-call` 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. — docs/README.md:37
docs/README.md links to `wiki/en/21-skyapm-tracing`, but `docs/wiki/en/21-skyapm-tracing` 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. — docs/README.md:41
docs/README.md links to `wiki/en/22-config-center`, but `docs/wiki/en/22-config-center` 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. — docs/README.md:42
docs/README.md links to `wiki/en/23-registry-center`, but `docs/wiki/en/23-registry-center` 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. — docs/README.md:43
docs/README.md links to `architecture/adnc-overall-architecture.svg`, but `docs/architecture/adnc-overall-architecture.svg` 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. — docs/README.md:47
docs/README.md links to `architecture/adr/ADR-001-modular-monolith-first`, but `docs/architecture/adr/ADR-001-modular-monolith-first` 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. — docs/README.md:48
docs/README_ZH.md links to `wiki/zh-cn/01-adnc-intro-zh`, but `docs/wiki/zh-cn/01-adnc-intro-zh` 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. — docs/README_ZH.md:9
docs/README_ZH.md links to `wiki/zh-cn/02-quickstart-zh`, but `docs/wiki/zh-cn/02-quickstart-zh` 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. — docs/README_ZH.md:10
docs/README_ZH.md links to `wiki/zh-cn/03-quickly-docker-deploy-zh`, but `docs/wiki/zh-cn/03-quickly-docker-deploy-zh` 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. — docs/README_ZH.md:11
docs/README_ZH.md links to `wiki/zh-cn/04-appsettings-zh`, but `docs/wiki/zh-cn/04-appsettings-zh` 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. — docs/README_ZH.md:15
docs/README_ZH.md links to `wiki/zh-cn/05-feature-dev-guide-zh`, but `docs/wiki/zh-cn/05-feature-dev-guide-zh` 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. — docs/README_ZH.md:16
docs/README_ZH.md links to `wiki/zh-cn/06-repository-dev-guide-zh`, but `docs/wiki/zh-cn/06-repository-dev-guide-zh` 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. — docs/README_ZH.md:17
docs/README_ZH.md links to `wiki/zh-cn/07-service-dev-guide`, but `docs/wiki/zh-cn/07-service-dev-guide` 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. — docs/README_ZH.md:18
docs/README_ZH.md links to `wiki/zh-cn/08-api-dev-guide-zh`, but `docs/wiki/zh-cn/08-api-dev-guide-zh` 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. — docs/README_ZH.md:19
docs/README_ZH.md links to `wiki/zh-cn/09-claims-based-authentication-zh`, but `docs/wiki/zh-cn/09-claims-based-authentication-zh` 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. — docs/README_ZH.md:20
docs/README_ZH.md links to `wiki/zh-cn/10-efcore-pemelo-curd-zh`, but `docs/wiki/zh-cn/10-efcore-pemelo-curd-zh` 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. — docs/README_ZH.md:24
docs/README_ZH.md links to `wiki/zh-cn/11-efcore-pemelo-codefirst-zh`, but `docs/wiki/zh-cn/11-efcore-pemelo-codefirst-zh` 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. — docs/README_ZH.md:25
docs/README_ZH.md links to `wiki/zh-cn/12-efcore-pemelo-sqlserver-zh`, but `docs/wiki/zh-cn/12-efcore-pemelo-sqlserver-zh` 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. — docs/README_ZH.md:26
docs/README_ZH.md links to `wiki/zh-cn/13-efcore-pemolo-unitofwork-zh`, but `docs/wiki/zh-cn/13-efcore-pemolo-unitofwork-zh` 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. — docs/README_ZH.md:27
docs/README_ZH.md links to `wiki/zh-cn/14-efcore-pemelo-sql-zh`, but `docs/wiki/zh-cn/14-efcore-pemelo-sql-zh` 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. — docs/README_ZH.md:28
docs/README_ZH.md links to `wiki/zh-cn/15-maxsale-readwritesplit-zh`, but `docs/wiki/zh-cn/15-maxsale-readwritesplit-zh` 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. — docs/README_ZH.md:29
What to do
Reconcile the README with reality: docs/README.md links to `wiki/en/01-adnc-intro`, but `docs/wiki/en/01-adnc-intro` does not exist; docs/README.md links to `wiki/en/02-quickstart`, but `docs/wiki/en/02-quickstart` does not exist; docs/README.md links to `wiki/en/03-quickly-docker-deploy`, but `docs/wiki/en/03-quickly-docker-deploy` does not exist; docs/README.md links to `wiki/en/04-appsettings`, but `docs/wiki/en/04-appsettings` does not exist; docs/README.md links to `wiki/en/05-feature-dev-guide`, but `docs/wiki/en/05-feature-dev-guide` does not exist.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Exemplary✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P2 · Observability7.1 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
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.
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.
Do you agree with this assessment?
P9 · Domain vs controller coverage7.4 / 10Exemplary✓ Tool-verified
Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.
Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.
What to do
Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
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.
11 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). (×10) — src/Infrastructures/Consul/Configuration/DefaultConsulConfigurationProvider.cs:15, src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:57, src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:63, …
`.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — REDACTED:74
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`dto.NewPassword == rePassword` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again. — src/Demo/Admin/Application/Validators/UserChangePwdDtoValidator.cs:20
This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything. (×3) — src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:80, src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:117, src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:112
DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes. (×2) — src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:96, src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:200
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×6) — REDACTED:21, REDACTED:20, REDACTED:21, …
No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×6) — REDACTED:21, REDACTED:20, REDACTED:21, …
What to do
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Demo/Admin/Application/Validators/UserChangePwdDtoValidator.cs:20`.
Authenticate ciphertext, do not just encrypt it: move to an AEAD cipher (`AesGcm`, `ChaCha20Poly1305`), or where the wire format is fixed, add encrypt-then-MAC with HMAC-SHA256 over IV+ciphertext under a separately derived key and verify the tag with `CryptographicOperations.FixedTimeEquals` before decrypting. Unauthenticated CBC is malleable, and a decrypt path that distinguishes padding failures from other failures is a padding oracle. This repository constructs symmetric encryption whose ciphertext nothing authenticates at 3 sites, not one: `src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:80` (CBC or another CipherMode member), `src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:117` (CBC or another CipherMode member), `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:112` (CBC or another CipherMode member). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Replace DES/3DES (and bare RijndaelManaged) with AES-GCM via `Aes.Create()`. This repository constructs a broken or deprecated cipher at 2 sites, not one: `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:96` (TripleDES), `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:200` (TripleDES). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×11) — src/Infrastructures/Consul/Configuration/DefaultConsulConfigurationProvider.cs:15, src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:57, src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:63, …
`Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead. (×2) — src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Bitmap.cs:32, src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Bitmap.cs:61
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.
`rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `CreateMachineKey` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw. — src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.MachineKey.cs:49
`ms` is a `MemoryStream`, which implements `IDisposable`, and it is created here (line 163). Every use of it in `ToPem` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ms = …;`), which releases it at the end of the scope on every path including a throw. — src/Infrastructures/Helper/Internal/Encrypt/Shared/RsaProvider.cs:163
`cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 106). Every use of it in `InternalInterceptSynchronous` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:106
`cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 147). Every use of it in `InternalInterceptAsynchronous` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:147
`cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 232). Every use of it in `InternalInterceptAsynchronous` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:232
`cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `RemoveCachesAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw. — src/Infrastructures/Redis.Caching/Core/Preheater/AbstractCacheService.cs:30
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 45/289 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×39) — REDACTED:21, REDACTED:41, REDACTED:51, …
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.
`catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:87, src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:199
`catch (DbUpdateConcurrencyException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Infrastructures/Repository.EfCore/Repositories/EfRepository.cs:108
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.3 `!` suppressions per 1k syntax nodes — 39 suppression(s) across the 148212 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
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 — 32 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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) — consul_client_1 Error context canceled nginx Error context canceled redis Error context canceled consul_server_1 Error context canceled grafana Error context canceled consul_server_2 Error context canceled consul_server_3 Error context canceled mariadb Error context canceled promtail Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: redis Pulling grafana Pulling mariadb Error Get "https://registry-1.docker.io/v2/": Forbidden loki Error context canceled rabbitmq Error context canceled consul_server_1 Error context canceled nginx Error context canceled redis Error context canceled promtail Error context canceled grafana Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D32 Data Compliance (PII/GDPR) — 130 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
ED5 Idempotency — 4 mutating command handler(s)/consumer(s) detected and 4 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — 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.
P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Domain depends on infrastructure: EntityInfo src/Demo/Ord/Domain/EntityConfig/EntityInfo.cs:7— `EntityInfo` (domain layer) names `ModelBuilder` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: OrderConfig src/Demo/Ord/Domain/EntityConfig/OrderConfig.cs:5— `OrderConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: OrderItemConfig src/Demo/Ord/Domain/EntityConfig/OrderItemConfig.cs:5— `OrderItemConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: EntityInfo src/Demo/Whse/Domain/EntityConfig/EntityInfo.cs:7— `EntityInfo` (domain layer) names `ModelBuilder` from `Microsoft.EntityFrameworkCore` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: ProductConfig src/Demo/Whse/Domain/EntityConfig/ProductConfig.cs:7— `ProductConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: WarehouseConfig src/Demo/Whse/Domain/EntityConfig/WarehouseConfig.cs:7— `WarehouseConfig` (domain layer) names `EntityTypeBuilder` from `Microsoft.EntityFrameworkCore.Metadata.Builders` — a persistence type (in a member signature). The domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: WarehouseManager src/Demo/Whse/Domain/Services/WarehouseManager.cs:39— `WarehouseManager` (domain layer) names `EntityFrameworkQueryableExtensions` from `Microsoft.EntityFrameworkCore` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
AnalyzerSeverityNone src/.editorconfig:146— ASP0025 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/.editorconfig:155— CA1305 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/.editorconfig:284— CA2007 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/.editorconfig:381— IDE0073 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/.editorconfig:389— IDE0130 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
NoWarnInCsproj src/Infrastructures/Redis/Providers/StackExchange/EasyCaching.Redis.csproj:25— 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
NoWarnInCsproj src/Directory.Build.props:16— 1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
NoWarnInCsproj src/Directory.Build.props:16— 0436 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
S1 · Web-Security Posture· Password hashing without a KDF · ×1
Password hashing without a KDF src/Demo/Admin/Application/Validators/UserChangePwdDtoValidator.cs:20— `dto.NewPassword == rePassword` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again.
X2 · Cancellation propagation· Async method without CancellationToken · ×39
Async method without CancellationToken: LoginAsync REDACTED:21— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LogoutAsync REDACTED:41— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RefreshAccessTokenAsync REDACTED:51— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ChangePassword REDACTED:92— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetUserValidatedInfoAsync REDACTED:102— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetCurrenUserPermissions REDACTED:118— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetUserProfileAsync REDACTED:150— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ChangeProfileAsync REDACTED:163— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync REDACTED:20— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync REDACTED:32— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync REDACTED:43— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync REDACTED:69— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetOptionsAsync REDACTED:82— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync src/Demo/Admin/Api/Controllers/DictDataController.cs:20— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync src/Demo/Admin/Api/Controllers/DictDataController.cs:32— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync src/Demo/Admin/Api/Controllers/DictDataController.cs:43— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync src/Demo/Admin/Api/Controllers/DictDataController.cs:68— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync REDACTED:20— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync REDACTED:32— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteAsync REDACTED:43— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync REDACTED:55— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetTreelistAsync REDACTED:69— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetMenusForRouterAsync REDACTED:78— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync REDACTED:20— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateAsync REDACTED:32— No CancellationToken parameter — this work can't be stopped early once started.
Dead code: CacheService src/Demo/Maint/Application/Cache/CacheService.cs:6— NamedType CacheService — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Maint.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: NlogLogDto src/Demo/Maint/Application/Contracts/Dtos/Log/NlogLogDto.cs:6— NamedType NlogLogDto — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Maint.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CacheService src/Demo/Whse/Application/Cache/CacheService.cs:5— NamedType CacheService — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Whse.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CahceConsts src/Demo/Whse/Application/Cache/CahceConsts.cs:3— NamedType CahceConsts — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Whse.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: WarehouseBlockQtyDto src/Demo/Whse/Application/Contracts/Dtos/Warehouse/WarehouseBlockQtyDto.cs:3— NamedType WarehouseBlockQtyDto — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Whse.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CacheService src/Demo/Ord/Application/Cache/CacheService.cs:5— NamedType CacheService — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Ord.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CahceConsts src/Demo/Ord/Application/Cache/CahceConsts.cs:3— NamedType CahceConsts — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Ord.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: OrderMarkCreatedStatusDto src/Demo/Ord/Application/Contracts/Dtos/Order/OrderMarkCreatedStatusDto.cs:3— NamedType OrderMarkCreatedStatusDto — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Ord.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MenuRepoExtension src/Demo/Admin/Repository/Extensions/MenuRepoExtension.cs:3— NamedType MenuRepoExtension — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Admin.Repository, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: RemoveBlockedQty src/Demo/Whse/Domain/Aggregates/WarehouseAggregate/Warehouse.cs:52— Method RemoveBlockedQty — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Whse.Domain, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Deliver src/Demo/Whse/Domain/Aggregates/WarehouseAggregate/Warehouse.cs:69— Method Deliver — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Whse.Domain, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AccountBloomFilter src/Demo/Admin/Application/Cache/AccountBloomFilter.cs:6— NamedType AccountBloomFilter — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Admin.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CacheKeyBloomFilter src/Demo/Admin/Application/Cache/CacheKeyBloomFilter.cs:6— NamedType CacheKeyBloomFilter — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Admin.Application, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetKeyValues src/Infrastructures/Repository.EfCore/Extensions/EntityEntryExtension.cs:7— Method GetKeyValues — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Infra.Repository.EfCore, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CacheService src/Demo/Cust/Api/Application/Cache/CacheService.cs:6— NamedType CacheService — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Cust.Api, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CahceConsts src/Demo/Cust/Api/Application/Cache/CahceConsts.cs:3— NamedType CahceConsts — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Demo.Cust.Api, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: LoginResponse src/ServiceShared/Remote/Http/Messages/LoginResponse.cs:3— NamedType LoginResponse — Roslyn's SymbolFinder walked every project the solution loads, including Adnc.Shared.Remote, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Sync-over-async blocking — 11 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/Consul/Configuration/DefaultConsulConfigurationProvider.cs:15— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:57— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:63— `.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 REDACTED:74— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:92— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:133— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:74— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:304— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:107— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:183— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:186— `.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) src/Infrastructures/Consul/Configuration/DefaultConsulConfigurationProvider.cs:15— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:57— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/EventBus/RabbitMq/ConnectionManager.cs:63— 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) REDACTED:59— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:92— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:133— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:74— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:304— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:107— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:183— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:186— 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.
TodoComment src/Demo/Cust/Api/Application/Subscribers/OrderPaidEventSubscriber.cs:33— //TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Infrastructures/Repository.EfCore.MongoDB/Transaction/MongoDbUnitOfWork.cs:3— //todo: implement MongoDbUnitOfWork — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ServiceShared/Application/Extensions/DependencyRegistrarExtension.cs:60— //todo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ServiceShared/Application/Extensions/DependencyRegistrarExtension.cs:68— //todo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ServiceShared/Application/Extensions/DependencyRegistrarExtension.cs:74— //todo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:67— //todo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:123— //todo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/ServiceShared/WebApi/Extensions/HostExtension.cs:25— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Change coupling: BaseRabbitMqConsumer.cs ↔ RabbitMqProducer.cs src/Infrastructures/EventBus/RabbitMq/BaseRabbitMqConsumer.cs:1— `src/Infrastructures/EventBus/RabbitMq/BaseRabbitMqConsumer.cs` and `src/Infrastructures/EventBus/RabbitMq/RabbitMqProducer.cs` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `35e57899` chore:Add `System.Text` and `System.Text.Json` namespace references.; `0cc1aa08` chore: Update XML comments and parameter names in multiple files; `1d19f93a` refactor: Refactored RabbitMQ connection management using ConnectionM… — run `git show` on any of them.
Change coupling: PermissionRemoteHandler.cs ↔ AbstractWebApiDependencyRegistrar.cs src/ServiceShared/WebApi/Authorization/Handlers/PermissionRemoteHandler.cs:1— `src/ServiceShared/WebApi/Authorization/Handlers/PermissionRemoteHandler.cs` and `src/ServiceShared/WebApi/Registrar/AbstractWebApiDependencyRegistrar.cs` change together 71% of the time (12 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `0437b7e9` refactor: Adjusted the file directory structure.; `42c2d4e2` [feat]PermissionAttribute => AdncAuthorizeAttribute [fix]Authorizatio… (at that commit the files were still `src/ServerApi/Services/Shared/Adnc.Shared.WebApi/Authorization/PermissionRemoteHandler.cs` and `src/ServerApi/Services/Shared/Adnc.Shared.WebApi/Registrar/AbstractWebApiDependencyRegistrar.cs`); `639259c6` [feat]BasicTokenGenerator获取userid逻辑优化 [feat]<ApiResponse<UserValidate… (at that commit the files were still `src/ServerApi/Services/Shared/Adnc.Shared.WebApi/Authorization/PermissionRemoteHandler.cs` and `src/ServerApi/Services/Shared/Adnc.Shared.WebApi/Registrar/AbstractWebApiDependencyRegistrar.cs`) — run `git show` on any of them.
Change coupling: HostExtension.cs ↔ WebApplicationBuilderExtension.cs src/ServiceShared/WebApi/Extensions/HostExtension.cs:1— `src/ServiceShared/WebApi/Extensions/HostExtension.cs` and `src/ServiceShared/WebApi/Extensions/WebApplicationBuilderExtension.cs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `b06727b2` fix:修复CA2201警告; `84ac3f41` refactor:更新配置类型常量及相关逻辑; `e725320b` feat:KestrelOptions.cs 移动到adnc.infra.consul项目 (at that commit the files were still `src/ServerApi/ServiceShared/Adnc.Shared.WebApi/Extensions/HostExtension.cs` and `src/ServerApi/ServiceShared/Adnc.Shared.WebApi/Extensions/WebApplicationBuilderExtension.cs`) — run `git show` on any of them.
Change coupling: LogConsumersHostedService.cs ↔ OperateLogAsyncInterceptor.cs src/ServiceShared/Application/Channels/LogConsumersHostedService.cs:1— `src/ServiceShared/Application/Channels/LogConsumersHostedService.cs` and `src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `8ae1866a` refactor:重构日志处理机制为通道实现; `a80b9128` feat:规范异常捕获代码; `afb6b94a` fix:消除代码警告 — run `git show` on any of them.
Change coupling: ConsulDiscoverDelegatingHandler.cs ↔ ServiceCollectionExtension.cs src/Infrastructures/Consul/Discover/Handler/ConsulDiscoverDelegatingHandler.cs:1— `src/Infrastructures/Consul/Discover/Handler/ConsulDiscoverDelegatingHandler.cs` and `src/Infrastructures/Consul/Extensions/ServiceCollectionExtension.cs` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `95f29add` fix:消除代码警告; `b06727b2` fix:修复CA2201警告; `ac45c9e6` change the foldername (at that commit the files were still `src/ServerApi/Infrastructures/Consul/Discover/Handler/ConsulDiscoverDelegatingHandler.cs` and `src/ServerApi/Infrastructures/Consul/Extensions/ServiceCollectionExtension.cs`) — run `git show` on any of them.
Change coupling: JwtTokenHelper.cs ↔ AbstractWebApiDependencyRegistrar.cs src/ServiceShared/WebApi/Authentication/Bearer/JwtTokenHelper.cs:1— `src/ServiceShared/WebApi/Authentication/Bearer/JwtTokenHelper.cs` and `src/ServiceShared/WebApi/Registrar/AbstractWebApiDependencyRegistrar.cs` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `0cc1aa08` chore: Update XML comments and parameter names in multiple files; `efe56b41` feat:JWTOptions.cs 移动到 Adnc.Shared.WebApi/Authentication/Bearer目录以及相关… (at that commit the files were still `src/ServerApi/ServiceShared/Adnc.Shared.WebApi/Authentication/Bearer/JwtTokenHelper.cs` and `src/ServerApi/ServiceShared/Adnc.Shared.WebApi/Registrar/AbstractWebApiDependencyRegistrar.cs`); `a5a5a545` [feta]认证/授权代码优化调整。 (at that commit the files were still `src/ServerApi/Services/Shared/Adnc.Shared.WebApi/Authentication/JwtBearer/JwtTokenHelper.cs` and `src/ServerApi/Services/Shared/Adnc.Shared.WebApi/Registrar/AbstractWebApiDependencyRegistrar.cs`) — run `git show` on any of them.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×6
Disposable created and abandoned in the method that made it src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.MachineKey.cs:49— `rng` is a `RandomNumberGenerator`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `CreateMachineKey` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var rng = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Infrastructures/Helper/Internal/Encrypt/Shared/RsaProvider.cs:163— `ms` is a `MemoryStream`, which implements `IDisposable`, and it is created here (line 163). Every use of it in `ToPem` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var ms = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:106— `cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 106). Every use of it in `InternalInterceptSynchronous` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:147— `cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 147). Every use of it in `InternalInterceptAsynchronous` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:232— `cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 232). Every use of it in `InternalInterceptAsynchronous` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Infrastructures/Redis.Caching/Core/Preheater/AbstractCacheService.cs:30— `cancelTokenSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `RemoveCachesAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var cancelTokenSource = …;`), which releases it at the end of the scope on every path including a throw.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:18— src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:18-31 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:42-56 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:67-82 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:95-109 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:257— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:257-286 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:321-350 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:385-407 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:442-464 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:26— src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:26-35 | src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:76-85 | src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:126-135 | src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:176-185 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:234— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:234-249 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:414-431 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:242-257 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:508-525 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Demo/Admin/Api/DependencyRegistrar.cs:12— src/Demo/Admin/Api/DependencyRegistrar.cs:12-31 | src/Demo/Cust/Api/DependencyRegistrar.cs:14-43 | src/Demo/Maint/Api/DependencyRegistrar.cs:12-29 | src/Demo/Ord/Api/DependencyRegistrar.cs:12-29 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (16 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:260— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:260-275 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:324-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:260` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:259— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:259-274 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:387-402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:259` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:323— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:323-338 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:444-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:323` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:27— src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:27-42 | src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:52-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Infrastructures/Repository.EfCore.Mysql/Transaction/MySQLUnitOfWork.cs:12— src/Infrastructures/Repository.EfCore.Mysql/Transaction/MySQLUnitOfWork.cs:12-27 | src/Infrastructures/Repository.EfCore.SqlServer/Transaction/SqlServerUnitOfWork.cs:12-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:33— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:33-39 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:139-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:417— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:417-423 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:511-517 — before extracting anything, compare `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs` and `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:140— src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:140-146 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:280-286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:140` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Infrastructures/Repository/Interceptor/Castle/UowAsyncInterceptor.cs:164— src/Infrastructures/Repository/Interceptor/Castle/UowAsyncInterceptor.cs:164-170 | src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:139-146 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/Demo/Admin/Application/Services/UserService.cs:266— src/Demo/Admin/Application/Services/UserService.cs:266-272 | src/Demo/Admin/Application/Services/UserService.cs:284-290 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Demo/Admin/Application/Services/UserService.cs:266` 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.
Cross-context type TrackerKind (Infrastructures → ServiceShared) src/ServiceShared/Application/Services/Trackers/DbMessageTrackerService.cs:10— TrackerKind (context Infrastructures) is exposed in ServiceShared's public surface via DbMessageTrackerService.Kind — couples the contexts.
Cross-context type TrackerKind (Infrastructures → ServiceShared) src/ServiceShared/Application/Services/Trackers/MessageTrackerFactory.cs:9— TrackerKind (context Infrastructures) is exposed in ServiceShared's public surface via MessageTrackerFactory.Create — couples the contexts.
Cross-context type TrackerKind (Infrastructures → ServiceShared) src/ServiceShared/Application/Services/Trackers/NullMessageTrackerService.cs:8— TrackerKind (context Infrastructures) is exposed in ServiceShared's public surface via NullMessageTrackerService.Kind — couples the contexts.
Cross-context type TrackerKind (Infrastructures → ServiceShared) src/ServiceShared/Application/Services/Trackers/RedisMessageTrackerService.cs:8— TrackerKind (context Infrastructures) is exposed in ServiceShared's public surface via RedisMessageTrackerService.Kind — couples the contexts.
TooManyMethods: DefaultRedisProvider src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs— TooManyMethods — 800 significant lines (blank, comment-only and punctuation-only lines excluded), 139 methods, declared across 13 files: StackExchange/DefaultRedisProvider.List.cs (28), StackExchange/DefaultRedisProvider.Hash.cs (22), StackExchange/DefaultRedisProvider.SortedSet.cs (18), StackExchange/DefaultRedisProvider.Set.cs (14), +9 more file(s). The bar is 30 methods; this is 109 over it, 4.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EncryptProivder src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs— TooManyMethods — 540 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods, declared across 8 files: Encrypt/EncryptProvider.Rsa.cs (28), Encrypt/EncryptProvider.Des.cs (10), Encrypt/EncryptProvider.Sha.cs (8), Encrypt/EncryptProivder.Aes.cs (7), +4 more file(s). The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstracCacheProvider src/Infrastructures/Redis.Caching/Provider/AbstracCacheProvider.cs— TooManyMethods — 383 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DefaultCachingProvider src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs— TooManyMethods — 352 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods, declared across 2 files: Provider/DefaultCachingProvider.cs (17), Provider/DefaultCachingProvider.Async.cs (16). The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (9 lines × 2) src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Geo.cs:12— src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Geo.cs:12-20 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Geo.cs:28-36 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/ServiceShared/Application/Channels/LogConsumersHostedService.cs:24— src/ServiceShared/Application/Channels/LogConsumersHostedService.cs:24-32 | src/ServiceShared/Application/Channels/LogConsumersHostedService.cs:67-75 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ServiceShared/Application/Channels/LogConsumersHostedService.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:189— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:189-197 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:235-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:244` calls `GetString` and `src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:198` 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 (9 lines × 2) src/Gateways/Ocelot/ThreadPoolSettings.cs:17— src/Gateways/Ocelot/ThreadPoolSettings.cs:17-25 | src/ServiceShared/WebApi/Extensions/HostExtension.cs:36-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Anemic entity: LoginLog src/ServiceShared/Repository/DapperEntities/LoginLog.cs:6— `LoginLog` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: OperationLog src/ServiceShared/Repository/DapperEntities/OperationLog.cs:6— `OperationLog` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: EventTracker src/ServiceShared/Repository/EfCoreEntities/EventTracker.cs:10— `EventTracker` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: AggregateRootWithBasicAuditInfo src/ServiceShared/Domain/Entities/AggregateRootWithBasicAuditInfo.cs:3— `AggregateRootWithBasicAuditInfo` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Duplicated block (15 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:388— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:388-402 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:445-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:388` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:77— src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:77-91 | src/Infrastructures/Redis/Providers/StackExchange/IDatabaseExtension.cs:98-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) src/ServiceShared/WebApi/Authorization/Handlers/PermissionCacheHandler.cs:13— src/ServiceShared/WebApi/Authorization/Handlers/PermissionCacheHandler.cs:13-27 | src/ServiceShared/WebApi/Authorization/Handlers/PermissionRemoteHandler.cs:7-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.String.cs:44— src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.String.cs:44-55 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.String.cs:63-74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:43— src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:43-54 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:96-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/Demo/Maint/Application/Services/LogService.cs:13— src/Demo/Maint/Application/Services/LogService.cs:13-24 | src/Demo/Maint/Application/Services/LogService.cs:37-48 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Geo.cs:81— src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Geo.cs:81-88 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Geo.cs:126-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:80— src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:80-87 | src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:114-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:57— src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:57-64 | src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:79-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
DM7 · Repository granularity· Repository contract exposes a live query handle · ×3
Repository contract exposes a live query handle: IEfBaseRepository src/Infrastructures/Repository/Interface/IEfBaseRepository.cs:7— `IEfBaseRepository` returns `IQueryable` from `Where`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked.
Repository contract exposes a live query handle: IEfRepository src/Infrastructures/Repository/Interface/IEfRepository.cs:10— `IEfRepository` returns `IQueryable` from `GetAll`, `GetAll`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked.
Repository contract exposes a live query handle: IMongoDbRepository src/Infrastructures/Repository/Interface/IMongoDbRepository.cs:3— `IMongoDbRepository` returns `IQueryable` from `Where`. That hands the caller the persistence engine rather than an aggregate: query composition, and with it the shape of what gets loaded, moves out of the repository and out of the aggregate's reach — and the contract can no longer be implemented by anything that is not that ORM. Return the aggregate (or a list of them) from methods that name the question being asked.
S1 · Web-Security Posture· Ciphertext is encrypted but not authenticated · ×3
Ciphertext is encrypted but not authenticated src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:80— This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything.
Ciphertext is encrypted but not authenticated src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:117— This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything.
Ciphertext is encrypted but not authenticated src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:112— This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything.
Swallowed exception (caught, then discarded) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:87— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:199— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Infrastructures/Repository.EfCore/Repositories/EfRepository.cs:108— `catch (DbUpdateConcurrencyException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:18— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:18-59 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:70-139 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:148-189 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:101-169 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:178-219 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) REDACTED:9— REDACTED:9-56 | REDACTED:9-52 | REDACTED:9-53 | src/Demo/Ord/Api/Program.cs:9-53 | src/Demo/Whse/Api/Program.cs:9-53 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (26 lines × 2) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:105— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:105-130 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:181-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:105` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (26 lines × 2) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:74— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:74-99 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:151-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:93— src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:93-103 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:199-209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:93` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Demo/Admin/Application.Contracts/Dtos/Dict/DictCreationDto.cs:37— src/Demo/Admin/Application.Contracts/Dtos/Dict/DictCreationDto.cs:37-62 | src/Demo/Admin/Repository/Entities/Dict.cs:30-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 3) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:21— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:21-29 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:74-82 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:151-159 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:72` calls `ThrowIfLEZero`, `nameof` and `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:19` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) src/Demo/Admin/Api/DependencyRegistrar.cs:13— src/Demo/Admin/Api/DependencyRegistrar.cs:13-21 | src/Demo/Maint/Api/DependencyRegistrar.cs:13-21 | src/Demo/Ord/Api/DependencyRegistrar.cs:13-21 — before extracting anything, compare `src/Demo/Admin/Api/DependencyRegistrar.cs` and `src/Demo/Maint/Api/DependencyRegistrar.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 (5 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:71— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:71-75 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:171-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/Demo/Admin/Application/Services/UserService.cs:319— src/Demo/Admin/Application/Services/UserService.cs:319-323 | src/Demo/Admin/Application/Services/UserService.cs:340-344 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 4) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:35— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:35-39 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:62-66 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:141-145 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:170-174 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 4) src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:27— src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:27-31 | src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:77-81 | src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:127-131 | src/Infrastructures/Redis.Caching/Core/Diagnostics/SkyApm/CacheTracingDiagnosticProcessor.cs:177-181 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `eventData` to `DiagnosticDataWrapper<BeforeGetRequestEventData>` in one and `DiagnosticDataWrapper<BeforeSetRequestEventData>` 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 (7 lines × 3) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:63— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:63-70 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:171-178 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:191-197 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: the declarations holding them bind `data` to `string` in one and `byte[]` 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 before the matched lines, `src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:62` calls `ThrowIfNullOrWhiteSpace`, `nameof`, `ThrowIfNotEqualLength` and `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:191` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:58— src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:58-64 | src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:80-87 | src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:114-121 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/ServiceShared/Application/Interceptors/OperateLog/OperateLogAsyncInterceptor.cs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:28— REDACTED:28-33 | REDACTED:86-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/Demo/Cust/Api/Application/Services/CustomerService.cs:77— src/Demo/Cust/Api/Application/Services/CustomerService.cs:77-82 | src/Demo/Cust/Api/Application/Services/CustomerService.cs:124-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Demo/Cust/Api/Application/Services/CustomerService.cs:77` 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.
CRAP 240: DataTimeExtension.GetDaysOfMonth src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:183— Cyclomatic 15 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 240: DataTimeExtension.GetDaysOfMonth src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:208— Cyclomatic 15 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 110: JsonConfigurationFileParser.VisitValue src/Infrastructures/Consul/Configuration/JsonConfigurationFileParser.cs:52— Cyclomatic 10 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 110: DataTimeExtension.In src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:301— Cyclomatic 10 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 90: DataTimeExtension.GetWeekChineseNameOfDay src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:234— Cyclomatic 9 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 90: DataTimeExtension.GetWeekNumberOfDay src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:254— Cyclomatic 9 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
Unfinished stub — throws NotImplementedException src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:228— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:255— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs· Both branches open with the same statements · ×2
Both branches open with the same statements — the condition does not decide them src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:14— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Both branches open with the same statements — the condition does not decide them src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hash.cs:155— The first 3 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
Unfinished stub — throws NotImplementedException src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:228— `LPushXAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:255— `RPushXAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Weak cipher src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:96— DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes.
Weak cipher src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:200— DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes.
Sync-over-async (deadlock risk) through `Task.WaitAll` src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Bitmap.cs:32— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
Sync-over-async (deadlock risk) through `Task.WaitAll` src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Bitmap.cs:61— `Task.WaitAll` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAll(…)` instead.
RSAKeyExtensions.FromLvccXmlString (cyclomatic 20) REDACTED:70— RSAKeyExtensions.FromLvccXmlString has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
No assertions: TestSpeed test/Unittest.Redis/TestCases/IdGeneraterTests.cs:46— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D17 · Explicit Debt· Whole file has no live code · ×1
Whole file has no live code — 3 debt markers inside it src/ServiceShared/WebApi/Authentication/Bearer/BearerAuthenticationHandler.cs:11— Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 3 debt markers (3 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 3 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Build failed — The target solution did not build cleanly (errors: 9), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0579: Duplicate 'global::System.Runtime.Versioning.TargetFrameworkAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyConfigurationAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyDescriptionAttribute' attribute; CS0579: Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute.
RSAKeyExtensions.FromLvccXmlString (cognitive 40) REDACTED:70— RSAKeyExtensions.FromLvccXmlString has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LogConsumersHostedService.ExecuteAsync (cognitive 26) src/ServiceShared/Application/Channels/LogConsumersHostedService.cs:5— LogConsumersHostedService.ExecuteAsync has cognitive complexity 26 (threshold 15). None of this is in the body itself: all 26 points belong to 2 function literals inside it that branch (lines 11, 54). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
RsaProvider.FromPem (cognitive 24) src/Infrastructures/Helper/Internal/Encrypt/Shared/RsaProvider.cs:18— RsaProvider.FromPem has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CachingAsyncInterceptor.InternalInterceptSynchronous (cognitive 23) src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:62— CachingAsyncInterceptor.InternalInterceptSynchronous has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (CachingAsyncInterceptor.InternalInterceptAsynchronous) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CachingAsyncInterceptor.InternalInterceptAsynchronous (cognitive 23) src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:184— CachingAsyncInterceptor.InternalInterceptAsynchronous has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (CachingAsyncInterceptor.InternalInterceptSynchronous) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AbstractPermissionHandler.HandleRequirementAsync (cognitive 23) src/ServiceShared/WebApi/Authorization/Handlers/AbstractPermissionHandler.cs:7— AbstractPermissionHandler.HandleRequirementAsync has cognitive complexity 23 (threshold 15). 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.
WebApplicationBuilderExtension.ReplacePlaceholder (cognitive 16) src/ServiceShared/WebApi/Extensions/WebApplicationBuilderExtension.cs:73— WebApplicationBuilderExtension.ReplacePlaceholder has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D20 · ADR Quality· No context/problem and no consequences/trade-offs; only the title 'ADR-002-outbox-pattern' is present · ×1
No context/problem and no consequences/trade-offs; only the title 'ADR-002-outbox-pattern' is present docs/architecture/adr/ADR-002-outbox-pattern.md— Add a Context section explaining why an outbox pattern is needed (e.g. decoupling event ingestion from business processing) and a Consequences section covering trade-offs like memory usage, complexity, and eventual consistency
D20 · ADR Quality· No context/problem and no consequences; the title is informative but the body is a single decision with no rationale or trade-offs · ×1
No context/problem and no consequences; the title is informative but the body is a single decision with no rationale or trade-offs docs/architecture/adr/ADR-003-no-distributed-transaction-coordinator.md— Add a Context section explaining why distributed transaction coordination matters (e.g. ACID across services) and a Consequences section covering operational complexity, latency, and failure modes
D20 · ADR Quality· No context/problem and no consequences/trade-offs; only the title "ADR-004-event-bus-abstraction" is informative · ×1
No context/problem and no consequences/trade-offs; only the title "ADR-004-event-bus-abstraction" is informative docs/architecture/adr/ADR-004-event-bus-abstraction.md— Add a Context section explaining why an event bus abstraction was needed (e.g. decoupling components, handling asynchronous events) and a Consequences section covering trade-offs like coupling to external systems or operational complexity
D20 · ADR Quality· No context/problem and no consequences/trade-offs; only the title 'ADR-005-redis-as-distributed-foundation' is informative · ×1
No context/problem and no consequences/trade-offs; only the title 'ADR-005-redis-as-distributed-foundation' is informative docs/architecture/adr/ADR-005-redis-as-distributed-foundation.md— Add a Context section explaining why Redis was chosen over alternatives (e.g. in-memory key-value store with persistence/cluster support) and a Consequences section covering operational complexity, latency tradeoffs against databases, and scaling requirements
D20 · ADR Quality· No context/problem and no consequences/trade-offs; only the title 'opentelemetry-observability' is informative · ×1
No context/problem and no consequences/trade-offs; only the title 'opentelemetry-observability' is informative docs/architecture/adr/ADR-006-opentelemetry-observability.md— State what observability needs are being addressed (e.g. distributed tracing, metrics collection) and why OTLP/GRPC instrumentation was chosen over alternatives, plus any operational or cost trade-offs of adopting OpenTelemetry
D22 · Internal API Consistency· Inconsistent search parameter types for paged queries. Some services (Dict, Role, SysConfig) use a generic `SearchPagedDto`, while others (DictData, User) use domain-specific search DTOs. This forces consumers to know which specific search DTO to instantiate for each entity, rather than using a unified search interface. · ×1
Inconsistent search parameter types for paged queries. Some services (Dict, Role, SysConfig) use a generic `SearchPagedDto`, while others (DictData, User) use domain-specific search DTOs. This forces consumers to know which specific search DTO to instantiate for each entity, rather than using a unified search interface. — Standardize on a single `SearchPagedDto` for all paged queries, or ensure all domain-specific search DTOs inherit from a common base interface that includes pagination properties, allowing a unified `GetPagedAsync<T>(ISearchInput input)` signature across all services. (signatures: IDictService.GetPagedAsync(SearchPagedDto input) | IDictDataService.GetPagedAsync(DictDataSearchPagedDto input) | IRoleService.GetPagedAsync(SearchPagedDto input) | ISysConfigService.GetPagedAsync(SearchPagedDto input) | IUserService.GetPagedAsync(UserSearchPagedDto input))
D22 · Internal API Consistency· Inconsistent naming and parameter structure for tree retrieval. `GetTreelistAsync` vs `GetTreeListAsync` (naming convention inconsistency · ×1
Inconsistent naming and parameter structure for tree retrieval. `GetTreelistAsync` vs `GetTreeListAsync` (naming convention inconsistency: 'Treelist' vs 'Tree List'). Furthermore, Menu accepts only keywords, while Organization accepts name and status, lacking a unified filter interface. — Unify the method name to `GetTreeListAsync` (camelCase or PascalCase consistently) and consider using a common `TreeSearchDto` or filter interface for parameters to allow consistent filtering logic across hierarchical entities. (signatures: IMenuService.GetTreelistAsync(string? keywords = null) | IOrganizationService.GetTreeListAsync(string? name = null, bool? status = null))
D22 · Internal API Consistency· Inconsistent naming for menu-related retrieval operations. `GetMenusForRouterAsync` implies a specific use case (router generation), while `GetMenuOptionsAsync` implies a UI dropdown use case. While distinct, the naming convention is inconsistent (`ForRouter` vs `Options`). · ×1
Inconsistent naming for menu-related retrieval operations. `GetMenusForRouterAsync` implies a specific use case (router generation), while `GetMenuOptionsAsync` implies a UI dropdown use case. While distinct, the naming convention is inconsistent (`ForRouter` vs `Options`). — Rename `GetMenusForRouterAsync` to `GetRouterTreeAsync` or `GetMenusForNavigationAsync` to better reflect the output type (`RouterTreeDto`) and align with the `GetMenuOptionsAsync` naming pattern (e.g., `Get...Async`). Alternatively, rename both to be more generic like `GetMenuTreeAsync` and `GetMenuOptionsAsync` if the distinction is clear from the return type. (signatures: IMenuService.GetMenusForRouterAsync(IEnumerable<long> roleIds) | IMenuService.GetMenuOptionsAsync(bool? onlyParent))
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (8 members, 50+ identical tokens) src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hyperloglog.cs:11— src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hyperloglog.cs:11-24 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hyperloglog.cs:27-40 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:34-47 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:125-138 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:172-185 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:265-278 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:11-30 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:117-136 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:32— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:32-49 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:59-92 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:138-156 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:167-205 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:70-78 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:170-178 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:190-225 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 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 7 times.
Duplicated block (61 lines × 2) src/Gateways/Ocelot/JWTOptions.cs:18— src/Gateways/Ocelot/JWTOptions.cs:18-78 | src/ServiceShared/WebApi/Authentication/Bearer/JWTOptions.cs:18-78 — before extracting anything, compare `src/Gateways/Ocelot/JWTOptions.cs` and `src/ServiceShared/WebApi/Authentication/Bearer/JWTOptions.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11–42 lines × 2) src/Infrastructures/Repository/Interface/IEfBaseRepository.cs:8— src/Infrastructures/Repository/Interface/IEfBaseRepository.cs:8-49 | src/Infrastructures/Repository/Interface/IMongoDbRepository.cs:4-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Repository/Interface/IEfBaseRepository.cs:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–31 lines × 2) src/ServiceShared/Repository/DapperEntities/LoginLog.cs:14— src/ServiceShared/Repository/DapperEntities/LoginLog.cs:14-26 | src/ServiceShared/Repository/DapperEntities/OperationLog.cs:36-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (24 lines × 2) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:166— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:166-189 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:196-219 — before extracting anything, compare `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs` and `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:166` 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 (20–21 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:59— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:59-78 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:167-187 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (20 lines × 2) src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:113— src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:113-132 | src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:156-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:113` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:89— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:89-107 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:120-138 — before extracting anything, compare `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs` and `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 3) src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:114— src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:114-130 | src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:157-173 | src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:243-259 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis.Caching/Core/Interceptor/Castle/CachingAsyncInterceptor.cs:114` 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 (15 lines × 4) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:260— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:260-274 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:324-338 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:388-402 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:445-459 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Rsa.cs:260` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:18— src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:18-30 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:67-81 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13–14 lines × 2) src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:99— src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:99-112 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:200-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:199` calls `MemoryStream`, `Create` and `src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:99` 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 (12 lines × 4) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:89— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:89-100 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:166-177 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:120-131 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:196-207 — before extracting anything, compare `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs` and `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 8) src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hyperloglog.cs:12— src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hyperloglog.cs:12-20 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Hyperloglog.cs:28-36 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:35-43 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:126-134 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:173-181 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:266-274 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:12-20 | src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Set.cs:118-126 — there are 8 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 8 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:343— src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:343-348 | src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:353-358 | src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:368-373 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–10 lines × 3) src/Gateways/Ocelot/ThreadPoolSettings.cs:30— src/Gateways/Ocelot/ThreadPoolSettings.cs:30-38 | src/ServiceShared/WebApi/Extensions/HostExtension.cs:49-57 | src/ServiceShared/WebApi/Extensions/HostExtension.cs:78-87 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Gateways/Ocelot/ThreadPoolSettings.cs:30` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `poolOptions` to `IOptions<ThreadPoolSettings>` in one and `IOptionsMonitor<ThreadPoolSettings>` 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 (9 lines × 4) src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:21— src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:21-29 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:46-54 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:71-80 | src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:99-107 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:43` calls `Parameter` and `src/Infrastructures/Core/Extensions/Expression/ExpressionLogicalOperatorsExtension .cs:18` 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 (8 lines × 3) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:235— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:235-242 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:243-250 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:509-516 — before extracting anything, compare `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs` and `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:235` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 4) src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:237— src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:237-243 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:417-423 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:245-251 | src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:511-517 — before extracting anything, compare `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs` and `src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:59— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:59-66 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:167-174 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:70-75 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:170-175 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `data` to `string` in one and `byte[]` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 6) src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:33— src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:33-39 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:60-66 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:139-145 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProivder.Aes.cs:168-174 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:71-75 | src/Infrastructures/Helper/Internal/Encrypt/EncryptProvider.Des.cs:171-175 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: the declarations holding them bind `data` to `string` in one and `byte[]` 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 (10 lines × 2) src/Infrastructures/EventBus/Extensions/ServiceCollectionExtension.cs:102— src/Infrastructures/EventBus/Extensions/ServiceCollectionExtension.cs:102-111 | src/Infrastructures/Redis.Caching/Extensions/ServiceCollectionExtension.cs:70-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (55 lines × 2) src/Demo/Admin/Application.Contracts/Dtos/Menu/MenuCreationDto.cs:16— src/Demo/Admin/Application.Contracts/Dtos/Menu/MenuCreationDto.cs:16-70 | src/Demo/Admin/Repository/Entities/Menu.cs:33-87 — 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 (36–39 lines × 5) REDACTED:18— REDACTED:18-56 | REDACTED:17-52 | REDACTED:18-53 | src/Demo/Ord/Api/Program.cs:18-53 | src/Demo/Whse/Api/Program.cs:18-53 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:18` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Demo/Maint/Api/DependencyRegistrar.cs:13— src/Demo/Maint/Api/DependencyRegistrar.cs:13-29 | src/Demo/Ord/Api/DependencyRegistrar.cs:13-29 — before extracting anything, compare `src/Demo/Maint/Api/DependencyRegistrar.cs` and `src/Demo/Ord/Api/DependencyRegistrar.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) src/Demo/Cust/Api/Application/Subscribers/CustomerRechargedEventSubscriber.cs:54— src/Demo/Cust/Api/Application/Subscribers/CustomerRechargedEventSubscriber.cs:54-67 | src/Demo/Cust/Api/Application/Subscribers/OrderPaidEventSubscriber.cs:38-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Demo/Cust/Api/Application/Subscribers/CustomerRechargedEventSubscriber.cs:54` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 4) src/Demo/Admin/Api/DependencyRegistrar.cs:14— src/Demo/Admin/Api/DependencyRegistrar.cs:14-21 | src/Demo/Cust/Api/DependencyRegistrar.cs:16-23 | src/Demo/Maint/Api/DependencyRegistrar.cs:14-21 | src/Demo/Ord/Api/DependencyRegistrar.cs:14-21 — before extracting anything, compare `src/Demo/Admin/Api/DependencyRegistrar.cs` and `src/Demo/Maint/Api/DependencyRegistrar.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.
Off the main sequence: Adnc.Infra.Core src/Infrastructures/Core/Adnc.Infra.Core.csproj:1— Adnc.Infra.Core: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
D8 · Code Coverage· No test project references Adnc.Shared.WebApi · ×1
No test project references Adnc.Shared.WebApi REDACTED— No test project in this repository references Adnc.Shared.WebApi (46 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Shared.Application · ×1
No test project references Adnc.Shared.Application src/ServiceShared/Application/Adnc.Shared.Application.csproj— No test project in this repository references Adnc.Shared.Application (23 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references EasyCaching.Redis · ×1
No test project references EasyCaching.Redis src/Infrastructures/Redis/Providers/StackExchange/EasyCaching.Redis.csproj— No test project in this repository references EasyCaching.Redis (16 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Infra.EventBus · ×1
No test project references Adnc.Infra.EventBus src/Infrastructures/EventBus/Adnc.Infra.EventBus.csproj— No test project in this repository references Adnc.Infra.EventBus (15 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Shared.Application.Contracts · ×1
No test project references Adnc.Shared.Application.Contracts src/ServiceShared/Application.Contracts/Adnc.Shared.Application.Contracts.csproj— No test project in this repository references Adnc.Shared.Application.Contracts (15 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Shared.Remote · ×1
No test project references Adnc.Shared.Remote src/ServiceShared/Remote/Adnc.Shared.Remote.csproj— No test project in this repository references Adnc.Shared.Remote (14 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Gateway.Ocelot · ×1
No test project references Adnc.Gateway.Ocelot REDACTED— No test project in this repository references Adnc.Gateway.Ocelot (8 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Shared.Domain · ×1
No test project references Adnc.Shared.Domain src/ServiceShared/Domain/Adnc.Shared.Domain.csproj— No test project in this repository references Adnc.Shared.Domain (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Shared.Repository · ×1
No test project references Adnc.Shared.Repository src/ServiceShared/Repository/Adnc.Shared.Repository.csproj— No test project in this repository references Adnc.Shared.Repository (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Infra.Repository.EfCore.SqlServer · ×1
No test project references Adnc.Infra.Repository.EfCore.SqlServer src/Infrastructures/Repository.EfCore.SqlServer/Adnc.Infra.Repository.EfCore.SqlServer.csproj— No test project in this repository references Adnc.Infra.Repository.EfCore.SqlServer (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Adnc.Shared · ×1
No test project references Adnc.Shared src/ServiceShared/Shared/Adnc.Shared.csproj— No test project in this repository references Adnc.Shared (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 35.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
CRAP 210: DataTimeExtension.GetDateFormat src/Infrastructures/Core/Extensions/DateTime/DataTimeExtension.cs:320— Cyclomatic 14 with 0.0% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
CRAP 87: RSAKeyExtensions.FromLvccXmlString REDACTED:70— Cyclomatic 20 with 44.9% file coverage — too complex for how untested it is (CRAP = CC²·(1−cov)³ + CC; ≥30 needs tests or simplification).
README/code drift docs/README.md:9— docs/README.md links to `wiki/en/01-adnc-intro`, but `docs/wiki/en/01-adnc-intro` 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 docs/README.md:10— docs/README.md links to `wiki/en/02-quickstart`, but `docs/wiki/en/02-quickstart` 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 docs/README.md:11— docs/README.md links to `wiki/en/03-quickly-docker-deploy`, but `docs/wiki/en/03-quickly-docker-deploy` 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 docs/README.md:15— docs/README.md links to `wiki/en/04-appsettings`, but `docs/wiki/en/04-appsettings` 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 docs/README.md:16— docs/README.md links to `wiki/en/05-feature-dev-guide`, but `docs/wiki/en/05-feature-dev-guide` 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 docs/README.md:17— docs/README.md links to `wiki/en/06-repository-dev-guide`, but `docs/wiki/en/06-repository-dev-guide` 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 docs/README.md:18— docs/README.md links to `wiki/en/07-service-dev-guide`, but `docs/wiki/en/07-service-dev-guide` 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 docs/README.md:19— docs/README.md links to `wiki/en/08-api-dev-guide`, but `docs/wiki/en/08-api-dev-guide` 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 docs/README.md:20— docs/README.md links to `wiki/en/09-claims-based-authentication`, but `docs/wiki/en/09-claims-based-authentication` 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 docs/README.md:24— docs/README.md links to `wiki/en/10-efcore-pemelo-curd`, but `docs/wiki/en/10-efcore-pemelo-curd` 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 docs/README.md:25— docs/README.md links to `wiki/en/11-efcore-pemelo-codefirst`, but `docs/wiki/en/11-efcore-pemelo-codefirst` 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 docs/README.md:26— docs/README.md links to `wiki/en/12-efcore-pemelo-sqlserver`, but `docs/wiki/en/12-efcore-pemelo-sqlserver` 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 docs/README.md:27— docs/README.md links to `wiki/en/13-efcore-pemolo-unitofwork`, but `docs/wiki/en/13-efcore-pemolo-unitofwork` 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 docs/README.md:28— docs/README.md links to `wiki/en/14-efcore-pemelo-sql`, but `docs/wiki/en/14-efcore-pemelo-sql` 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 docs/README.md:29— docs/README.md links to `wiki/en/15-maxsale-readwritesplit`, but `docs/wiki/en/15-maxsale-readwritesplit` 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 docs/README.md:33— docs/README.md links to `wiki/en/16-snowflake-max_value-wokerid`, but `docs/wiki/en/16-snowflake-max_value-wokerid` 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 docs/README.md:34— docs/README.md links to `wiki/en/17-cache-redis-distributedlock-bloomfilter`, but `docs/wiki/en/17-cache-redis-distributedlock-bloomfilter` 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 docs/README.md:35— docs/README.md links to `wiki/en/18-service-http-call`, but `docs/wiki/en/18-service-http-call` 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 docs/README.md:36— docs/README.md links to `wiki/en/19-service-grpc-call`, but `docs/wiki/en/19-service-grpc-call` 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 docs/README.md:37— docs/README.md links to `wiki/en/20-service-event-call`, but `docs/wiki/en/20-service-event-call` 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 docs/README.md:41— docs/README.md links to `wiki/en/21-skyapm-tracing`, but `docs/wiki/en/21-skyapm-tracing` 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 docs/README.md:42— docs/README.md links to `wiki/en/22-config-center`, but `docs/wiki/en/22-config-center` 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 docs/README.md:43— docs/README.md links to `wiki/en/23-registry-center`, but `docs/wiki/en/23-registry-center` 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 docs/README.md:47— docs/README.md links to `architecture/adnc-overall-architecture.svg`, but `docs/architecture/adnc-overall-architecture.svg` 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 docs/README.md:48— docs/README.md links to `architecture/adr/ADR-001-modular-monolith-first`, but `docs/architecture/adr/ADR-001-modular-monolith-first` 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.
Commented-out code src/Gateways/Ocelot/ThreadPoolSettings.cs:17— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/EventBus/RabbitMq/RabbitMqProducer.cs:11— 8 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/EventBus/RabbitMq/RabbitMqProducer.cs:60— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/EventBus/RabbitMq/RabbitMqProducer.cs:62— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Helper/Internal/Encrypt/Shared/RsaProvider.cs:20— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Helper/Internal/Encrypt/Shared/RsaProvider.cs:21— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Helper/Internal/Encrypt/Shared/RsaProvider.cs:22— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/IdGenerater/Extensions/ServiceCollectionExtension.cs:18— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:316— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:318— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:321— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:322— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:324— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:326— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:328— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:330— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs:332— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:230— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:232— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:233— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:257— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:259— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.List.cs:260— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Repository.Dapper/Extensions/ServiceCollectionExtension.cs:21— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/Infrastructures/Repository.Dapper/Extensions/ServiceCollectionExtension.cs:22— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected REDACTED:21— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected REDACTED:20— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected REDACTED:21— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Demo/Ord/Api/Program.cs:21— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Demo/Whse/Api/Program.cs:21— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/Gateways/Ocelot/Program.cs:8— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:21— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected REDACTED:20— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected REDACTED:21— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Demo/Ord/Api/Program.cs:21— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Demo/Whse/Api/Program.cs:21— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
No app-layer HTTPS enforcement detected src/Gateways/Ocelot/Program.cs:8— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
Duplicated predicate src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:21— `!_cacheOptions.Value.PenetrationSetting.Disable && _redisOptions.Value.EnableBloomFilter` appears character-identically in 2 files — src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs, src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Infrastructures/Repository.EfCore/Repositories/AbstractEfBaseRepository.cs:61— `entry.State == EntityState.Added || entry.State == EntityState.Deleted` appears character-identically in 2 files — src/Infrastructures/Repository.EfCore.MongoDB/Repositories/MongoDbRepository.cs, src/Infrastructures/Repository.EfCore/Repositories/AbstractEfBaseRepository.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ServiceShared/WebApi/Authorization/Handlers/PermissionCacheHandler.cs:13— `requestPermissions == null || !requestPermissions.Any()` appears character-identically in 2 files — src/ServiceShared/WebApi/Authorization/Handlers/PermissionCacheHandler.cs, src/ServiceShared/WebApi/Authorization/Handlers/PermissionRemoteHandler.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs:443— `timeSpan is not null && timeSpan.HasValue` appears character-identically in 2 files — src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.Async.cs, src/Infrastructures/Redis.Caching/Provider/DefaultCachingProvider.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Infrastructures/EventBus/Extensions/ServiceCollectionExtension.cs:81— `type.IsAssignableTo(serviceType) && type.IsNotAbstractClass(true)` appears character-identically in 3 files — src/Infrastructures/EventBus/Extensions/ServiceCollectionExtension.cs, src/Infrastructures/Repository.EfCore/Extensions/ServiceCollectionExtension.cs, src/ServiceShared/Application/Registrar/AbstractApplicationDependencyRegistrar.DomainSerivces.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.
Fat interface: IEventPublisher (16 members) src/Infrastructures/EventBus/IEventPublisher.cs:3— `IEventPublisher` declares 16 members under just 4 distinct name(s): `PublishAsync`, `PublishAsync`, `Publish`, `Publish`, `PublishDelayAsync`, `PublishDelayAsync`, `PublishDelay`, `PublishDelay`, `PublishAsync`, `PublishAsync`, `Publish`, `Publish`, `PublishDelayAsync`, `PublishDelayAsync`, `PublishDelay`, `PublishDelay`. 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 16 separate responsibilities: a caller binds to 4 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 16 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: IAdoQuerierRepository (22 members) src/Infrastructures/Repository/Interface/IAdoQuerierRepository.cs:3— `IAdoQuerierRepository` declares 22 members under just 5 distinct name(s): `QueryAsync`, `QueryAsync`, `QueryFirstAsync`, `QueryFirstOrDefaultAsync`, `QuerySingleAsync`, `QuerySingleOrDefaultAsync`, `QueryFirstAsync`, `QueryFirstOrDefaultAsync`, `QuerySingleAsync`, `QuerySingleOrDefaultAsync`, `QueryAsync`, `QueryFirstAsync`, `QueryFirstOrDefaultAsync`, `QuerySingleAsync`, `QuerySingleOrDefaultAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`, `QueryAsync`. 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 22 separate responsibilities: a caller binds to 5 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 22 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: IRedisProvider (134 members) src/Infrastructures/Redis/IRedisProvider.cs:12— `IRedisProvider` declares 134 members: `Serializer`, `KeyDel`, `KeyDelAsync`, `KeyExpire`, `KeyExpireAsync`, `KeyExistsAsync`, `KeyExists`, `TTL`, `TTLAsync`, `IncrBy`, `IncrByAsync`, `IncrByFloat`, `IncrByFloatAsync`, `StringSet`, `StringSetAsync`, `StringGet`, `StringGetAsync`, `StringLen`, `StringLenAsync`, `StringSetRange`, `StringSetRangeAsync`, `StringGetRange`, `StringGetRangeAsync`, `HMSet`, `HSet`, `HExists`, `HDel`, `HGet`, `HGetAll`, `HIncrBy`, `HKeys`, `HLen`, `HVals`, `HMGet`, `HMSetAsync`, `HSetAsync`, `HExistsAsync`, `HDelAsync`, `HGetAsync`, `HGetAllAsync`, and 94 more. 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 134 declarations carry 127 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 127 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: ICacheProvider (23 members) src/Infrastructures/Redis.Caching/ICacheProvider.cs:7— `ICacheProvider` declares 23 members: `Name`, `CacheOptions`, `Serializer`, `Set`, `SetAsync`, `Get`, `GetAsync`, `Remove`, `RemoveAsync`, `ExistsAsync`, `Exists`, `TrySet`, `TrySetAsync`, `SetAll`, `SetAllAsync`, `RemoveAll`, `RemoveAllAsync`, `Get`, `GetAsync`, `RemoveByPrefix`, `RemoveByPrefixAsync`, `GetAsync`, `KeyExpireAsync`. 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 23 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 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.
Pass-through layer src/Demo/Whse/Api/Controllers/ProductController.cs:10— ProductController: all 7 public methods forward their arguments unchanged to productSrv and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call productSrv directly, or give the layer a job.
Pass-through layer src/Demo/Whse/Api/Controllers/WarehouseController.cs:10— WarehouseController: all 3 public methods forward their arguments unchanged to warehouseSrv and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call warehouseSrv directly, or give the layer a job.
Pass-through layer src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Locker.cs:8— DefaultRedisProvider: all 4 public methods forward their arguments unchanged to _redisDb and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _redisDb directly, or give the layer a job.
DM2 · Strongly-typed ids· Primitive id on a domain type · ×3
Primitive id on a domain type: LoginLog.UserId src/ServiceShared/Repository/DapperEntities/LoginLog.cs:16— `LoginLog.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that.
Primitive id on a domain type: OperationLog.UserId src/ServiceShared/Repository/DapperEntities/OperationLog.cs:41— `OperationLog.UserId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that.
Primitive id on a domain type: EventTracker.EventId src/ServiceShared/Repository/EfCoreEntities/EventTracker.cs:12— `EventTracker.EventId` is a raw `Int64` — give it a strongly-typed id: a dedicated single-field type wrapping the `Int64`, in whatever form your language spells that.
Thin analysable surface across projects: Adnc.Demo.Whse.Migrations src/Demo/Whse/Migrations/Adnc.Demo.Whse.Migrations.csproj— 2 project(s) carry only a thin slice of real code; `Adnc.Demo.Whse.Migrations` has 0 significant line(s). The mean analysable-surface weight is 90 %; this project lowers Solution Shape by about 0.4 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: Adnc.Demo.Ord.Migrations src/Demo/Ord/Migrations/Adnc.Demo.Ord.Migrations.csproj— 2 project(s) carry only a thin slice of real code; `Adnc.Demo.Ord.Migrations` has 0 significant line(s). The mean analysable-surface weight is 90 %; this project lowers Solution Shape by about 0.4 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
D21 · Naming Consistency· Inconsistent spelling of the word 'Generator'. The codebase uses 'Generater' (missing the second 'e') in several symbols related to ID generation and hash consistency, while the standard spelling is 'Generator'. · ×1
Inconsistent spelling of the word 'Generator'. The codebase uses 'Generater' (missing the second 'e') in several symbols related to ID generation and hash consistency, while the standard spelling is 'Generator'. — Rename 'Generater' to 'Generator' in all affected symbols (e.g., ServiceCollectionExtension.AddAdncInfraYitterIdGenerator, IdGenerator, HashConsistentGenerator). (symbols: Microsoft.Extensions.DependencyInjection.ServiceCollectionExtension.AddAdncInfraYitterIdGenerater, Adnc.Infra.IdGenerater.Yitter.IdGenerater.GetNextId, Adnc.Infra.IdGenerater.Yitter.IdGenerater.GetNextIdString, Adnc.Infra.Helper.Internal.HashConsistentGenerater._virtualNode, Adnc.Infra.Helper.Internal.HashConsistentGenerater._virtualNodeMultiple)
D21 · Naming Consistency· Typo in the class name 'EncryptProivder'. The word 'Provider' is misspelled as 'Proivder' across all methods in this class. · ×1
Typo in the class name 'EncryptProivder'. The word 'Provider' is misspelled as 'Proivder' across all methods in this class. — Rename the class 'EncryptProivder' to 'EncryptProvider' and update all method fully qualified names accordingly. (symbols: Adnc.Infra.Helper.Internal.Encrypt.EncryptProivder.RSADecrypt, Adnc.Infra.Helper.Internal.Encrypt.EncryptProivder.DESDecrypt, Adnc.Infra.Helper.Internal.Encrypt.EncryptProivder.AESEncrypt, Adnc.Infra.Helper.Internal.Encrypt.EncryptProivder.AESDecrypt, Adnc.Infra.Helper.Internal.Encrypt.EncryptProivder.RSAEncrypt)
D21 · Naming Consistency· Typo in the class name 'DocumenationExtension'. The word 'Documentation' is misspelled as 'Documenation' (missing 't'). · ×1
Typo in the class name 'DocumenationExtension'. The word 'Documentation' is misspelled as 'Documenation' (missing 't'). — Rename the class 'DocumenationExtension' to 'DocumentationExtension'. (symbols: System.Reflection.DocumenationExtension.GetSummary, System.Reflection.DocumenationExtension)
D21 · Naming Consistency· Inconsistent spelling of 'Cache'. The class 'CahceConsts' misspells 'Cache' as 'Cahce', while other caching-related classes use the correct spelling 'Cache'. · ×1
Inconsistent spelling of 'Cache'. The class 'CahceConsts' misspells 'Cache' as 'Cahce', while other caching-related classes use the correct spelling 'Cache'. — Rename the class 'CahceConsts' to 'CacheConsts'. (symbols: Adnc.Demo.Cust.Api.Application.Cache.CahceConsts, Adnc.Infra.Redis.Caching.Core.Diagnostics.DiagnosticDataWrapper, Adnc.Infra.Redis.Caching.Core.Diagnostics.SkyApm.CacheTracingDiagnosticProcessor, Adnc.Infra.Redis.Caching.Core.Diagnostics.CachingDiagnosticListenerExtensions)
D21 · Naming Consistency· Inconsistent naming for constant holder classes. Some use 'Consts' (plural) while others use 'ConstValue' (singular) or 'Consts' in different contexts. Specifically, 'RouteConsts' and 'PermissionConsts' use the plural form, while 'CachingConstValue' uses a singular noun phrase. While not a strict typo, the pattern is inconsistent across similar utility classes. · ×1
Inconsistent naming for constant holder classes. Some use 'Consts' (plural) while others use 'ConstValue' (singular) or 'Consts' in different contexts. Specifically, 'RouteConsts' and 'PermissionConsts' use the plural form, while 'CachingConstValue' uses a singular noun phrase. While not a strict typo, the pattern is inconsistent across similar utility classes. — Standardize on 'Consts' for classes holding multiple constants (e.g., rename 'CachingConstValue' to 'CachingConsts'). (symbols: Adnc.Demo.Maint.Api.RouteConsts, Adnc.Demo.Admin.Api.PermissionConsts, Adnc.Infra.Redis.Caching.Core.CachingConstValue)
D21 · Naming Consistency· Typo in property name 'DeliveryInfomaton'. The word 'Information' is misspelled as 'Infomaton' (missing 'r'). Other DTOs use 'Updation' which is a valid (though less common than 'Update') noun form, but this specific property has a clear typo. · ×1
Typo in property name 'DeliveryInfomaton'. The word 'Information' is misspelled as 'Infomaton' (missing 'r'). Other DTOs use 'Updation' which is a valid (though less common than 'Update') noun form, but this specific property has a clear typo. — Rename property 'DeliveryInfomaton' to 'DeliveryInformation'. (symbols: Adnc.Demo.Ord.Application.Contracts.Dtos.Order.OrderUpdationDto.DeliveryInfomaton, Adnc.Demo.Admin.Application.Contracts.Dtos.User.UserProfileUpdationDto, Adnc.Demo.Admin.Application.Contracts.Dtos.SysConfig.SysConfigUpdationDto)
D21 · Naming Consistency· Typo in DTO name 'ProducChangePriceDto'. The word 'Product' is misspelled as 'Produc' (missing 't'). Other product-related DTOs are spelled correctly. · ×1
Typo in DTO name 'ProducChangePriceDto'. The word 'Product' is misspelled as 'Produc' (missing 't'). Other product-related DTOs are spelled correctly. — Rename the class 'ProducChangePriceDto' to 'ProductChangePriceDto'. (symbols: Adnc.Demo.Whse.Application.Contracts.Dtos.Product.ProducChangePriceDto, Adnc.Demo.Whse.Application.Contracts.Dtos.Product.ProductCreationDto, Adnc.Demo.Whse.Application.Contracts.Dtos.Product.ProductPutOnSaleDto)
D21 · Naming Consistency· Inconsistent casing/abbreviation style for 'RSA'. While 'RSA' is an acronym and correctly capitalized, the surrounding class name 'EncryptProivder' has a typo. However, looking at 'AESDecrypt' and 'AESEncrypt', the acronym handling is consistent. The main issue here is the typo in the class name 'EncryptProivder' which affects all these methods. Since this is already captured in the 'EncryptProivder' finding, this is a duplicate context. · ×1
Inconsistent casing/abbreviation style for 'RSA'. While 'RSA' is an acronym and correctly capitalized, the surrounding class name 'EncryptProivder' has a typo. However, looking at 'AESDecrypt' and 'AESEncrypt', the acronym handling is consistent. The main issue here is the typo in the class name 'EncryptProivder' which affects all these methods. Since this is already captured in the 'EncryptProivder' finding, this is a duplicate context. — See 'EncryptProivder' finding. (symbols: Adnc.Infra.Helper.Internal.Encrypt.EncryptProivder.RSADecrypt, Adnc.Infra.Helper.Internal.Encrypt.EncryptProivder.RSAEncrypt)
D21 · Naming Consistency· Inconsistent naming convention for permission constants. 'Dict.Update' uses a simple noun-verb format, while 'Log.SearchForOperationLog' uses a verb-noun phrase with 'SearchFor'. This suggests a lack of consistent verb choice for permission actions. · ×1
Inconsistent naming convention for permission constants. 'Dict.Update' uses a simple noun-verb format, while 'Log.SearchForOperationLog' uses a verb-noun phrase with 'SearchFor'. This suggests a lack of consistent verb choice for permission actions. — Standardize permission constant names to a consistent verb-noun pattern (e.g., 'Dict.Update' and 'Log.SearchOperationLog'). (symbols: Adnc.Demo.Admin.Api.PermissionConsts.Dict.Update, Adnc.Demo.Maint.Api.PermissionConsts.Log.SearchForOperationLog)
D28 · Secrets (history)· Rotate the exposed credentials · ×1
ED3 · Event naming· Event not named in past tense · ×1
Event not named in past tense: EventEntity src/Infrastructures/EventBus/BaseEvent.cs:37— `EventEntity` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
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.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 45/289 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.3 `!` suppressions per 1k syntax nodes — 39 suppression(s) across the 148212 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Silent fallback default on unknown code src/Infrastructures/Redis/Providers/StackExchange/DefaultRedisProvider.Geo.cs:161— `GetGeoUnit` maps every unrecognised code to `GeoUnit.Meters`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
Off the main sequence: Adnc.Shared src/ServiceShared/Shared/Adnc.Shared.csproj:1— Adnc.Shared: abstractness 0.14, instability 0.00, distance 0.86 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 130 file(s) — `REDACTED`, `REDACTED`, `src/Demo/Admin/Api/Controllers/DictDataController.cs`, `REDACTED`, `REDACTED`, … (+125 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a16118-b27e-7190-ac1a-b64fd96e6fe8 · 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 — 10 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 145 · Warnings: 395 · Recommendations: 136 · Info: 41 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 00:52 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.