linfx/LinFx

Executive summary

linfx/LinFx scores 34 out of 100 and is rated Provisional, while four of its seven lenses score higher still: Architecture at 97, Event-Driven at 100, Performance at 56, and Code Health at 53. The score is provisional because the code didn't build, so the ratings may change once it does.

The score is lower than those four because the weakest lens counts most, and here that is Production Readiness, which scores 17 and is rated Critical. The project has no automated tests and no secret scanning results, so its Code Coverage and REDACTED Scanning dimensions score 0 out of 10, and until those dimensions reach 4, Production Readiness can't be rated higher than Adequate. Resolving the leaked secrets and adding automated tests are therefore the first actions, and if Production Readiness rose to 70, the score would rise from 34 to about 47.

Forty findings are critical: eleven empty catch blocks, eight high CVEs in dependencies, five unfinished stubs, three namespace dependency cycles, three NoWarnInCsproj entries, two vulnerable dependencies, two leaked secrets, two write-only private fields, one file-scoped pragma disable, one secret in history, one lack of automated tests, and one cryptographic key material that is a compile-time constant. A critical security finding is open.

Watchdog couldn't measure runtime accessibility because the service exited before it opened a port, so that dimension is left out of the score. The product code is 34,356 lines, which would take an estimated 0.3 person-years, around €49,000, to rebuild.

Code Health 53 Adequate, capped by Solution Shape and Structured logging Architecture 97 ★ Exemplary Maturity 39 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 17 ⚠ Critical, capped by Code Coverage, Test Distribution, Dependency Hygiene, REDACTED Scanning, CI/CD gates, Security & performance tooling and Outbound HTTP resilience Security and Compliance 46 Weak, capped by Data Protection and Web-Security Posture Event-Driven 100 ★ Exemplary Performance 56 Adequate

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 for The 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.

Production Readiness 17 · counts for 46%Maturity 39 · counts for 25%Security and Compliance 46 · counts for 14%Code Health 53 · counts for 8%Performance 56 · counts for 4%Architecture 97 · counts for 2%Event-Driven 100 · counts for 1%

If Production Readiness rose from 17 to 70, the lowest score rated Strong, the score would rise from 34 to about 47.

Code composition: what the lines of code are

Business logic 27%Supporting code 69%Generated by tools 4%

New since the last survey: 261 findings

These 261 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.

REDACTED Scanning · REDACTED
Explicit Debt · EmptyCatchBlock src/LinFx.Extensions.Kafka/KafkaMessageConsumer.cs
Explicit Debt · Dead code: PagedFilterResultRequest src/LinFx/Application/Dtos/PagedFilterResultRequest.cs
Explicit Debt · Dead code: AwaitableConcurrentQueue src/LinFx/Collections/Concurrent/AwaitableConcurrentQueue.cs
Explicit Debt · Dead code: AsNameValueCollection src/LinFx/Collections/IReadableStringCollectionExtensions.cs
Explicit Debt · Dead code: AsNameValueCollection src/LinFx/Collections/IReadableStringCollectionExtensions.cs
Explicit Debt · Dead code: SelectTry src/LinFx/Collections/LinqSelectExtensions.cs
Explicit Debt · Dead code: OnCaughtException src/LinFx/Collections/LinqSelectExtensions.cs
Explicit Debt · Dead code: OnCaughtException src/LinFx/Collections/LinqSelectExtensions.cs
Explicit Debt · Dead code: AddRepository src/LinFx/Domain/DependencyInjection/ICommonDbContextRegistrationOptionsBuilder.cs
Explicit Debt · Dead code: SetDefaultRepositoryClasses src/LinFx/Domain/DependencyInjection/ICommonDbContextRegistrationOptionsBuilder.cs
Explicit Debt · Dead code: FullAuditedAggregateRoot src/LinFx/Domain/Entities/Auditing/FullAuditedAggregateRoot.cs
Explicit Debt · Dead code: FullAuditedEntity src/LinFx/Domain/Entities/Auditing/FullAuditedEntity.cs
Explicit Debt · Dead code: FullAuditedEntity src/LinFx/Domain/Entities/Auditing/FullAuditedEntity.cs
Explicit Debt · Dead code: IsEntityWithId src/LinFx/Domain/Entities/EntityHelper.cs
Explicit Debt · Dead code: HasDefaultId src/LinFx/Domain/Entities/EntityHelper.cs
Explicit Debt · Dead code: CreateEqualityExpressionForId src/LinFx/Domain/Entities/EntityHelper.cs
Explicit Debt · Dead code: AddNamespace src/LinFx/Domain/Entities/Events/Distributed/AutoEntityDistributedEventSelectorListExtensions.cs
Explicit Debt · Dead code: AddAll src/LinFx/Domain/Entities/Events/Distributed/AutoEntityDistributedEventSelectorListExtensions.cs
Explicit Debt · Dead code: IExtendableObject src/LinFx/Domain/Entities/IExtendableObject.cs
Explicit Debt · Dead code: BasicRepositoryBase src/LinFx/Domain/Repositories/BasicRepositoryBase.cs
Explicit Debt · Dead code: GetCountAsync src/LinFx/Domain/Repositories/IReadOnlyBasicRepository.cs
Explicit Debt · Dead code: GetPagedListAsync src/LinFx/Domain/Repositories/IReadOnlyBasicRepository.cs
Explicit Debt · Dead code: WithDetailsAsync src/LinFx/Domain/Repositories/IReadOnlyRepository.cs
Explicit Debt · Dead code: WithDetailsAsync src/LinFx/Domain/Repositories/IReadOnlyRepository.cs
Explicit Debt · Dead code: ISupportsExplicitLoading src/LinFx/Domain/Repositories/ISupportsExplicitLoading.cs
Explicit Debt · Dead code: RepositoryBase src/LinFx/Domain/Repositories/RepositoryBase.cs
Explicit Debt · Dead code: ValueEquals src/LinFx/Domain/Values/ValueObject.cs
Explicit Debt · Dead code: IAuditSerializer src/LinFx/Extensions/Auditing/IAuditSerializer.cs
Explicit Debt · Dead code: AlwaysAllowPermissionChecker src/LinFx/Extensions/Authorization/Permissions/AlwaysAllowPermissionChecker.cs
Explicit Debt · Dead code: GetGroupOrNull src/LinFx/Extensions/Authorization/Permissions/IPermissionDefinitionContext.cs
Explicit Debt · Dead code: WithProperty src/LinFx/Extensions/Authorization/Permissions/PermissionDefinition.cs
Explicit Debt · Dead code: WithProviders src/LinFx/Extensions/Authorization/Permissions/PermissionDefinition.cs
Explicit Debt · Dead code: GetOrAddAsync src/LinFx/Extensions/Caching/DistributedCacheExtensions.cs
Explicit Debt · Dead code: GetOrAddAsync src/LinFx/Extensions/Caching/IDistributedCache.cs
Explicit Debt · Dead code: GetOrAddMany src/LinFx/Extensions/Caching/IDistributedCache.cs
Explicit Debt · Dead code: GetOrAddManyAsync src/LinFx/Extensions/Caching/IDistributedCache.cs
Explicit Debt · Dead code: Paging src/LinFx/Extensions/Data/Paging.cs
Explicit Debt · Dead code: ToSorting src/LinFx/Extensions/Data/SortingExtensions.cs
Explicit Debt · Dead code: AutowiredService src/LinFx/Extensions/DependencyInjection/AutowiredService.cs
Explicit Debt · Dead code: ServiceProviderAccessor src/LinFx/Extensions/DependencyInjection/ServiceProviderAccessor.cs
Explicit Debt · Dead code: LocalDistributedEventBus src/LinFx/Extensions/EventBus/Distributed/LocalDistributedEventBus.cs
Explicit Debt · Dead code: UseRetryStrategy src/LinFx/Extensions/EventBus/EventBusOptions.cs
Explicit Debt · Dead code: LocalEventErrorHandler src/LinFx/Extensions/EventBus/Local/LocalEventErrorHandler.cs
Explicit Debt · Dead code: MapCodeNamespace src/LinFx/Extensions/ExceptionHandling/Localization/ExceptionLocalizationOptions.cs
Explicit Debt · Dead code: WithProperty src/LinFx/Extensions/Features/FeatureDefinition.cs
Explicit Debt · Dead code: WithProperty src/LinFx/Extensions/Features/FeatureGroupDefinition.cs
Explicit Debt · Dead code: GetGroupOrNull src/LinFx/Extensions/Features/IFeatureDefinitionContext.cs
Explicit Debt · Dead code: RemoveGroup src/LinFx/Extensions/Features/IFeatureDefinitionContext.cs
Explicit Debt · Dead code: Audio src/LinFx/Extensions/Http/MimeTypes.cs
Explicit Debt · Dead code: Video src/LinFx/Extensions/Http/MimeTypes.cs
Explicit Debt · Dead code: GetByExtension src/LinFx/Extensions/Http/MimeTypes.cs
Explicit Debt · Dead code: IUser src/LinFx/Extensions/Identity/IUser.cs
Explicit Debt · Dead code: ServiceConfigurationContext src/LinFx/Extensions/Modularity/ServiceConfigurationContext.cs
Explicit Debt · Dead code: TenantIdWrapper src/LinFx/Extensions/MultiTenancy/TenantIdWrapper.cs
Explicit Debt · Dead code: ConfigureModule src/LinFx/Extensions/ObjectExtending/Modularity/ModuleExtensionConfigurationDictionaryExtensions.cs
Explicit Debt · Dead code: ConfigureEntity src/LinFx/Extensions/ObjectExtending/Modularity/ModuleExtensionConfigurationExtensions.cs
Explicit Debt · Dead code: ModuleExtensionConfigurationHelper src/LinFx/Extensions/ObjectExtending/Modularity/ModuleExtensionConfigurationHelper.cs
Explicit Debt · Dead code: Modules src/LinFx/Extensions/ObjectExtending/ModuleObjectExtensionManagerExtensions.cs
Explicit Debt · Dead code: GetExtendedObjects src/LinFx/Extensions/ObjectExtending/ObjectExtensionManager.cs
Explicit Debt · Dead code: GetValidationAttributes src/LinFx/Extensions/ObjectExtending/ObjectExtensionPropertyInfoExtensions.cs
Explicit Debt · Dead code: DefaultObjectMapper src/LinFx/Extensions/ObjectMapping/DefaultObjectMapper.cs
Explicit Debt · Dead code: WithProperty src/LinFx/Extensions/Setting/SettingDefinition.cs
Explicit Debt · Dead code: WithProviders src/LinFx/Extensions/Setting/SettingDefinition.cs
Explicit Debt · Dead code: IsTrueAsync src/LinFx/Extensions/Setting/SettingProviderExtensions.cs
Explicit Debt · Dead code: IsAsync src/LinFx/Extensions/Threading/AsyncHelper.cs
Explicit Debt · Dead code: SetScoped src/LinFx/Extensions/Threading/AsyncLocalSimpleScopeExtensions.cs
Explicit Debt · Dead code: AsyncLock src/LinFx/Extensions/Threading/AsyncLock.cs
Explicit Debt · Dead code: TaskExtensions src/LinFx/Extensions/Threading/TaskExtensions.cs
Explicit Debt · Dead code: TimingSettingProvider src/LinFx/Extensions/Timing/TimingSettingProvider.cs
Explicit Debt · Dead code: AddItem src/LinFx/Extensions/Uow/UnitOfWorkExtensions.cs
Explicit Debt · Dead code: GetItemOrDefault src/LinFx/Extensions/Uow/UnitOfWorkExtensions.cs
Explicit Debt · Dead code: RemoveItem src/LinFx/Extensions/Uow/UnitOfWorkExtensions.cs
Explicit Debt · Dead code: New src/LinFx/Linq/PredicateOperator.cs
Explicit Debt · Dead code: New src/LinFx/Linq/PredicateOperator.cs
Explicit Debt · Dead code: Extend src/LinFx/Linq/PredicateOperator.cs
Explicit Debt · Dead code: Extend src/LinFx/Linq/PredicateOperator.cs
Explicit Debt · Dead code: GetAttributesOfMemberOrDeclaringType src/LinFx/Reflection/ReflectionHelper.cs
Explicit Debt · Dead code: GetValueByPath src/LinFx/Reflection/ReflectionHelper.cs
Explicit Debt · Dead code: GetFullNameWithAssemblyName src/LinFx/Reflection/TypeExtensions.cs
Explicit Debt · Dead code: IsFunc src/LinFx/Reflection/TypeHelper.cs
Explicit Debt · Dead code: IsFunc src/LinFx/Reflection/TypeHelper.cs
Explicit Debt · Dead code: IsEnumerable src/LinFx/Reflection/TypeHelper.cs
Explicit Debt · Dead code: IsDictionary src/LinFx/Reflection/TypeHelper.cs
Explicit Debt · Dead code: StripNullable src/LinFx/Reflection/TypeHelper.cs
Explicit Debt · Dead code: FindTenantId src/LinFx/Security/Claims/ClaimsIdentityExtensions.cs
Explicit Debt · Dead code: FindClientId src/LinFx/Security/Claims/ClaimsIdentityExtensions.cs
Explicit Debt · Dead code: GetAllClaims src/LinFx/Security/Users/ICurrentUser.cs
Explicit Debt · Dead code: IsInRole src/LinFx/Security/Users/ICurrentUser.cs
Explicit Debt · Dead code: ToBase64Bytes src/LinFx/Utils/Base64Utils.cs
Explicit Debt · Dead code: CryptoUtils src/LinFx/Utils/CryptoUtils.cs
Explicit Debt · Dead code: CsvConverter src/LinFx/Utils/CsvConverter.cs
Explicit Debt · Dead code: IsValidCultureCode src/LinFx/Utils/CultureHelper.cs
Explicit Debt · Dead code: GetBaseCultureName src/LinFx/Utils/CultureHelper.cs
Explicit Debt · Dead code: CurrencyUtils src/LinFx/Utils/CurrencyUtils.cs
Explicit Debt · Dead code: MoneyUtils src/LinFx/Utils/CurrencyUtils.cs
Explicit Debt · Dead code: ToUnixTimestamp src/LinFx/Utils/DateTimeUtils.cs
Explicit Debt · Dead code: IsWeekend src/LinFx/Utils/DateTimeUtils.cs
Explicit Debt · Dead code: IsWeekday src/LinFx/Utils/DateTimeUtils.cs
Explicit Debt · Dead code: EncryptUtils REDACTED

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: 1 finding

This critical or serious finding was in the previous survey, on 7 October 2026, and is gone from this one.

Exception handling · Swallowed exception (caught, then discarded) src/LinFx.Extensions.EntityFrameworkCore/ValueConverters/ExtraPropertiesValueConverter.cs

Rebuild cost: about €49,000 · Estimate

Cost to rebuild	€16,000 to €82,000, for 269 to 861 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem	Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 34. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 34,356 lines of product code, of which 44% is declarations and boilerplate, 28% straight logic and 28% logic with branches
Comment lines	The estimate prices 26,752 lines. Comment lines count towards the size of 34,356 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.

Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.

Raises the score by about 13 points · Low effort · REDACTED Scanning

Resolve the 1 No automated tests finding(s) in Code Coverage.

Raises the score by about 13 points · Low effort · Code Coverage

Resolve the 1 No tests found finding(s) in Test Distribution.

Raises the score by about 13 points · Low effort · Test Distribution

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: CS0246: The type or namespace name 'JetBrains' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'NotNullAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'NotNull' could not be found (are you missing a using directive or an assembly reference?); CS1503: Argument 6: cannot convert from 'LinFx.Extensions.Timing.IClock' to 'Microsoft.Extensions.Internal.ISystemClock'; CS0246: The type or namespace name 'CanBeNullAttribute' could not be found (are you missing a using directive or an assembly reference?)

Based on: Solution Shape

Where the investment is most exposed · Value at risk

This code would cost about €49,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 17 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

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.

115 modules, with 285 dependencies between them. 3 loops run through 32 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 75 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.
uses →	1 LinFx.Collections	2 LinFx.Extensions.ExceptionHandling	3 LinFx.Extensions.ObjectExtending	4 LinFx.Domain.Entities	5 LinFx.Extensions.Data	6 LinFx.Extensions.MultiTenancy	7 LinFx.Extensions.Threading	8 LinFx.Extensions.Uow	9 LinFx.Security.Claims	10 LinFx.Extensions.EventBus.Local	11 LinFx.Security.Users	12 LinFx.Extensions.Auditing	13 LinFx.Extensions.EventBus.Distributed	14 LinFx.Extensions.Setting	15 LinFx.Extensions.EventBus	16 LinFx.Extensions.Timing	17 LinFx.Domain.Entities.Events	18 LinFx.Extensions.EntityFrameworkCore	19 LinFx.Extensions.EntityFrameworkCore.DependencyInjection	21 Microsoft.Extensions.DependencyInjection	22 LinFx.Extensions.Modularity	23 LinFx.Extensions.Caching	24 LinFx.Extensions.DynamicProxy	25 LinFx.Extensions.DependencyInjection	26 LinFx	28 LinFx.Extensions.Authorization.Permissions	29 LinFx.Extensions.MongoDB	30 LinFx.Domain.Repositories.MongoDB	31 LinFx.Extensions.Authorization	34 LinFx.Extensions.Features	35 LinFx.Application.Services	36 LinFx.Domain.Repositories
1 LinFx.Collections
2 LinFx.Extensions.ExceptionHandling
3 LinFx.Extensions.ObjectExtending
4 LinFx.Domain.Entities			2
5 LinFx.Extensions.Data																					1			2
6 LinFx.Extensions.MultiTenancy																					1			1
7 LinFx.Extensions.Threading																					1			1
8 LinFx.Extensions.Uow																					1		2	4
9 LinFx.Security.Claims																								1
10 LinFx.Extensions.EventBus.Local	1					1		3							12
11 LinFx.Security.Users									1															1
12 LinFx.Extensions.Auditing			6	1		2	1				3										1		2	2
13 LinFx.Extensions.EventBus.Distributed	2					1		1		3					8
14 LinFx.Extensions.Setting	1					1					1														1
15 LinFx.Extensions.EventBus	1		1			1		5		4			1								1
16 LinFx.Extensions.Timing														2										1
17 LinFx.Domain.Entities.Events								2		1		1	1		3
18 LinFx.Extensions.EntityFrameworkCore				1	1	1		2		1		2	1			1	2		3		1			2
19 LinFx.Extensions.EntityFrameworkCore.DependencyInjection																		1		2				1
20 LinFx.Extensions.EntityFrameworkCore.Uow					1	1	2	6										2
21 Microsoft.Extensions.DependencyInjection																			1					7	5
22 LinFx.Extensions.Modularity	1																			1				2	12
23 LinFx.Extensions.Caching						1	1	1													1
24 LinFx.Extensions.DynamicProxy																					1
25 LinFx.Extensions.DependencyInjection	2																						2
26 LinFx		2																			2			1
27 LinFx.Extensions.AspNetCore.ExceptionHandling		2		1																				5
28 LinFx.Extensions.Authorization.Permissions	1								1															4
29 LinFx.Extensions.MongoDB																					1			4
30 LinFx.Domain.Repositories.MongoDB				1	1	1				1		1	1				1										1					2
31 LinFx.Extensions.Authorization									1												1		2	2		3
32 LinFx.Extensions.EventBus.Kafka						1		3					2		3	1					1			1	1
33 LinFx.Extensions.EventBus.RabbitMQ						1		3					2		3	1					1			1	1
34 LinFx.Extensions.Features	1								2												1		2	8	1
35 LinFx.Application.Services					1	1		2			1	1		1										2					1	1
36 LinFx.Domain.Repositories					1	1	1	2																2				1
37 LinFx.Extensions.FeatureManagement	1			2					2									1				1		5	2	2				5
38 LinFx.Extensions.AuditLogging		1	5	5								9									1											1
39 LinFx.Extensions.PermissionManagement	1			1		3												1			2	2				9					1
40 LinFx.Extensions.TenantManagement																		1			1					2					1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 53% · Adequate · gated by D18, X4 ·

The Good

D1 · .NET / C# Cyclomatic Complexity 9.1 D2 · .NET / C# Cognitive Complexity 7.4 D3 · .NET / C# God Classes 9.3 D4 · .NET / C# Code Duplication 9.7 GD1 · Repo Unfinished & placeholder code 10.0 X1 · Repo Async correctness 7.6 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X5 · Repo Nullable reference types 9.1

The Bad

IC1 · Repo Incompleteness & stubs 6.6 X2 · Repo Cancellation propagation 6.5 X23 · Repo Unguarded diagnostic materialisation 5.1 X3 · Repo Exception handling 5.2

The Ugly

D17 · .NET / C# Explicit Debt 4.6 D18 · .NET / C# Solution Shape 3.0 X18 · Repo Disposal-pattern correctness 4.7 X4 · Repo Structured logging 3.5

At a glance — Architecture · 97% · Exemplary ·

The Good

D5 · .NET / C# Coupling 9.6 D6 · .NET / C# Cohesion (LCOM4) 9.9 D23 · .NET / C# Boundary Type-Coupling 9.6 D26 · .NET / C# Project Cohesion 9.0 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.8 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9

The Bad

D27 · .NET / C# Navigability 7.0

The Ugly

D22 · .NET / C# Internal API Consistency 3.0

At a glance — Maturity · 39% · Weak · gated by D34, M2 ·

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 7.0 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 9.0 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 10.0

The Bad

M1 · Repo Documentation (README) 6.1

The Ugly

D20 · .NET / C# ADR Quality 0.0 D34 · .NET / C# Knowledge Freshness 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 17% · Critical · gated by D8, D9, D12, D13, P1, P3, P7 ·

The Good

D14 · .NET / C# License Compliance 10.0 P8 · Repo Schema migrations 10.0

The Bad

P10 · Repo Library API & versioning 6.0 P2 · Repo Observability 5.4 P6 · Repo Release Hygiene 5.0

The Ugly

D8 · .NET / C# Code Coverage 0.0 D12 · .NET / C# Dependency Hygiene 3.3 D13 · .NET / C# REDACTED Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 46% · Weak · gated by C1, S1 ·

The Good

D28 · .NET / C# Secrets (history) 9.0 D44 · .NET / C# Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 C3 · Repo Audit Trail 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D29 · .NET / C# Static Analysis (SAST) 5.6

The Ugly

D30 · .NET / C# Dependency Vulnerabilities 4.8 C1 · Repo Data Protection 3.5 S1 · Repo Web-Security Posture 0.0

At a glance — Event-Driven · 100% · Exemplary ·

The Good

ED1 · Repo Handler temporal coupling 10.0

At a glance — Performance · 56% · Adequate ·

The Bad

PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.9

The Ugly

PF3 · Repo Async & latency hygiene 4.5

Security & Compliance — OWASP Top-10 mapping

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	11	Medium
A03:2025 — Software Supply Chain Failures	9	High / Critical
A07:2025 — Authentication Failures	4	High / Critical

Roadmap

Immediately resolve the two leaked secrets in REDACTED and REDACTED to secure sensitive credentials, followed by addressing the two vulnerable dependencies to mitigate external risks. Next, establish automated testing by covering the identified gaps in code coverage and ensuring tests are properly distributed across the project. Finally, update the deprecated REDACTED dependency to maintain long-term stability and compatibility.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.	+13.4 pts	Low	REDACTED Scanning
Resolve the 1 No automated tests finding(s) in Code Coverage.	+13.4 pts	Low	Code Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.	+13.4 pts	Low	Test Distribution
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.	+12.3 pts	Low	Dependency Hygiene
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED.	+7.6 pts	Low	Dependency Hygiene
Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED.	+7.6 pts	Low	Dependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+3.4 pts	Low	ADR Quality
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+3.5 pts	Medium	Architecture documentation

File quality

Per-file score 0–10 — a quality signature. Of 204 files carrying findings, judged against the Production bar: 1% slop · 41% mixed · 58% near-clean.

File	Score	Band	Worst signal
REDACTED	0.2	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	3.3	Slop	Dependency Vulnerabilities: High CVE: REDACTED
src/LinFx/Extensions/ObjectMapping/DefaultObjectMapper.cs	4.1	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
src/LinFx/Extensions/Authorization/AuthorizationPolicyProvider.cs	4.9	Mixed	Explicit Debt: WriteOnlyPrivateField
REDACTED	5.1	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	5.4	Mixed	Static Analysis (SAST): Medium: REDACTED
src/LinFx/Extensions/Uow/UnitOfWork.cs	5.8	Mixed	Explicit Debt: EmptyCatchBlock
src/LinFx/Reflection/TypeFinder.cs	5.8	Mixed	Explicit Debt: EmptyCatchBlock
common.props	5.8	Mixed	Explicit Debt: NoWarnInCsproj
REDACTED	5.8	Mixed	Static Analysis (SAST): Medium: REDACTED
src/LinFx/Reflection/TypeHelper.cs	6.0	Mixed	Explicit Debt: Dead code: IsFunc
src/LinFx/Utils/StringExtensions.cs	6.0	Mixed	Explicit Debt: Dead code: EnsureStartsWith
src/LinFx/Domain/Entities/EntityHelper.cs	6.0	Mixed	Explicit Debt: CommentedOutCode
src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs	6.0	Mixed	Explicit Debt: CommentedOutCode
src/LinFx.Extensions.EntityFrameworkCore/EfDbContext.cs	6.0	Mixed	Explicit Debt: CommentedOutCode
src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs	6.0	Mixed	Explicit Debt: CommentedOutCode
src/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs	6.0	Mixed	Explicit Debt: CommentedOutCode
src/LinFx.Extensions.AuditLogging/Domain/IAuditLogRepository.cs	6.0	Mixed	Explicit Debt: Dead code: IAuditLogRepository
src/LinFx/Domain/Repositories/BasicRepositoryBase.cs	6.0	Mixed	Explicit Debt: Dead code: BasicRepositoryBase

How the grades work

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 — 40

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 — 540

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 — 271

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 5

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 74 of 80 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 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 — 80 dimensions across the health lenses

D1D2D3D4D5D6D8D9D12D13D14D15D17D18D19D20D21D22D23D24D26D27D28D29D30D34D35D44AX1AX10AX2AX3AX5AX6C1C2C3ED1GD1IC1M1M2M3M4P1P10P2P3P6P7P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 799 of 851 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a160f9-31ad-79b4-8793-6e5e2729d30f.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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.

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 (2 contributor(s) across 627 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% 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. `src/LinFx.Extensions.AspNetCore.Authentication.WeChat/CachedPropertiesDataFormat.cs`, `src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs`, `src/LinFx.Extensions.AspNetCore/Auditing/AuditingMiddleware.cs`, `src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultHttpExceptionStatusCodeFinder.cs`, `src/LinFx.Extensions.AspNetCore/ExceptionHandling/ExceptionHandlingMiddleware.cs`, … (+101 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 — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged 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 ToolchainServer (src/LinFx.Extensions.FeatureManagement.HttpApi). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'LinFx.Extensions.FeatureManagement.HttpApi.csproj'`: Unable to proceed with project 'src/LinFx.Extensions.FeatureManagement.HttpApi/LinFx.Extensions.FeatureManagement.HttpApi.csproj'. Ensure you have…; runtime evidence skipped (launch chosen because src/LinFx.Extensions.FeatureManagement.HttpApi/LinFx.Extensions.FeatureManagement.HttpApi.csproj is a Microsoft.NET.Sdk.Web project).
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. 287 further occurrence(s) are not listed individually; the score already reflects all 327.
PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 427 further occurrence(s) are not listed individually; the score already reflects all 467.
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. 109 further occurrence(s) are not listed individually; the score already reflects all 149.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
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.
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.
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.
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 (6): D19, D21, D22, D24, D26, 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.

Dimensions

D1 · Cyclomatic Complexity9.1 / 10Stronggated by 5 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Prevented

5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TypeHelper.GetSimplifiedName at 25.

TypeHelper.GetSimplifiedName (cyclomatic 25)src/LinFx/Reflection/TypeHelper.cs:188

RSAKeyExtensions.FromLvccXmlString (cyclomatic 19)REDACTED:369

StringExtensions.ToSnakeCase (cyclomatic 17)src/LinFx/Utils/StringExtensions.cs:288

EntityHistoryHelper.IsBaseAuditProperty (cyclomatic 17)src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:269

EntityHistoryHelper.ShouldSavePropertyHistory (cyclomatic 16)src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:213

What to do

Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TypeHelper.GetSimplifiedName (cyclomatic 25), RSAKeyExtensions.FromLvccXmlString (cyclomatic 19), StringExtensions.ToSnakeCase (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Do you agree with this assessment?

D2 · Cognitive Complexity7.4 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.4 / 10 · rule-coverage 100% · ceiling Prevented

20 method(s) exceeded the cognitive complexity threshold of 15; the worst was RSAKeyExtensions.FromLvccXmlString at 39.

RSAKeyExtensions.FromLvccXmlString (cognitive 39)REDACTED:369

ExtensibleObjectMapper.CanMapProperty (cognitive 32)src/LinFx/Extensions/ObjectExtending/ExtensibleObjectMapper.cs:161

DistributedCache.GetOrAddMany (cognitive 26)src/LinFx/Extensions/Caching/DistributedCache.cs:484

DistributedCache.GetOrAddManyAsync (cognitive 26)src/LinFx/Extensions/Caching/DistributedCache.cs:581

MongoModelBuilder.Build (cognitive 25)src/LinFx.Extensions.MongoDB/MongoModelBuilder.cs:27

+ 15 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with RSAKeyExtensions.FromLvccXmlString (cognitive 39), ExtensibleObjectMapper.CanMapProperty (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 7.4 to about 7.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 6 serious findings✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Prevented

6 god class(es) detected.

TooManyMethods: AsyncQueryableExecuter · ×5src/LinFx/Linq/AsyncQueryableExecuter.cs

FileTooLong: Caching/DistributedCache.cssrc/LinFx/Extensions/Caching/DistributedCache.cs

What to do

Resolve the 5 TooManyMethods finding(s) in God Classes — start with AsyncQueryableExecuter.cs, MongoDbAsyncQueryableProvider.cs, MongoDbRepository.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with DistributedCache.cs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Do you agree with this assessment?

D4 · Code Duplication9.7 / 10Stronggated by 20 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

19 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.

Duplicated block (13 lines × 2) · ×3src/LinFx/Extensions/Caching/DistributedCache.cs:1259

Duplicated block (14 lines × 2) · ×2src/LinFx/Extensions/ObjectExtending/Modularity/ExtensionPropertyConfiguration.cs:15

Duplicated block (10 lines × 2) · ×2src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:146

Duplicated block (6 lines × 2) · ×2src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:133

Members sharing a duplicated core (4 members, 50+ identical tokens)src/LinFx/Extensions/Caching/DistributedCache.cs:165

+ 10 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with DistributedCache.cs, NullDistributedEventBus.cs, IAuditLogRepository.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with ExtensionPropertyConfiguration.cs, FeatureManager.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with PermissionStore.cs, BasicRepositoryBase.cs. — One of this dimension's main actionable groups (2 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Prevented

21 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

Off the main sequence: LinFx.Extensions.EntityFrameworkCoresrc/LinFx.Extensions.EntityFrameworkCore/LinFx.Extensions.EntityFrameworkCore.csproj:1

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling — start with LinFx.Extensions.EntityFrameworkCore.csproj. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 96 classes have LCOM4 above 3.

Low cohesion: CommonDbContextRegistrationOptions (LCOM4 4)src/LinFx/Domain/DependencyInjection/CommonDbContextRegistrationOptions.cs:10

What to do

Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with CommonDbContextRegistrationOptions.cs. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

No automated tests — no test code was found in this repository.

No automated tests

What to do

Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D9 · Test Distribution0.0 / 10Critical✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No test suite found.

No tests found

What to do

Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D12 · Dependency Hygiene3.3 / 10Weak✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 3.3 / 10 · rule-coverage 100% · ceiling Verified

25 outdated, 2 vulnerable, 1 deprecated packages.

Vulnerable: Microsoft.Extensions.Caching.Memory · ×2

Deprecated: System.IdentityModel.Tokens.JwtREDACTED:30

Outdated: Swashbuckle.AspNetCoreREDACTED:17

Outdated: Microsoft.AspNetCore.Authorization · ×24

What to do

Resolve the 2 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Prevented

2 secret(s) detected.

REDACTED

What to do

Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 252 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 31 direct `PackageReference`(s), and 219 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt4.6 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.6 / 10 · rule-coverage 100% · ceiling Prevented

199 deducted debt markers + 173 dead symbols across 34356 LoC in the .NET projects (2.7/KLoC) → score 4.6.

EmptyCatchBlock · ×11src/LinFx.Extensions.Kafka/ConsumerPool.cs:78

NoWarnInCsproj · ×3common.props:6

WriteOnlyPrivateField · ×2src/LinFx.Extensions.AspNetCore.Authentication.WeChat/CachedPropertiesDataFormat.cs:15

FileScopedPragmaDisablesrc/LinFx.Extensions.EntityFrameworkCore/DependencyInjection/DbContextOptionsFactory.cs:111

Dead code: PagedFilterResultRequest · ×173src/LinFx/Application/Dtos/PagedFilterResultRequest.cs:8

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 11 EmptyCatchBlock finding(s) in Explicit Debt — start with UnitOfWork.cs (3), ConsumerPool.cs, KafkaMessageConsumer.cs. — One of this dimension's main actionable groups (11 issue-level).
Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with common.props (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CachedPropertiesDataFormat.cs, AuthorizationPolicyProvider.cs. — One of this dimension's main actionable groups (2 issue-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Maturity: Documented → Verified → Prevented · effective 3.0 / 10 · rule-coverage 100% · ceiling Documented

19 projects, 855 source files, 32955 hand-written lines of code (32955 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 1039 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 26 inter-project edges (build failed).

Build failed

What to do

Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

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.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

The repository's root README is a strong overview of the project (what it is and its DDD/EDA features) plus an explicit 'LinFx.Extensions' section listing Polly, FluentValidation, and Metrics packages with their feature subsets. It also documents installation via Nuget and development environment requirements. The samples directory README is a focused deployment guide for that directory rather than the repository as a whole; it does not contradict or depend on any code in the main repo. However there are gaps: no architecture/design docs (the summary counts zero of them), only an unstructured 'Samples' section with no ordering and no headings, so the outline is visible but navigable content is missing, and the samples directory README omits a contributing/guidance note.

XML-doc coverage: LinFx · ×21REDACTED

What to do

Improve Documentation Quality — currently 7.0/10. — The repository's root README is a strong overview of the project (what it is and its DDD/EDA features) plus an explicit 'LinFx.Extensions' section listing Polly, FluentValidation, and Metrics packages with their feature subsets. It also documents installation via Nuget and development environment requirements. The samples directory README is a focused deployment guide for that directory rather than the repository as a whole; it does not contradict or depend on any code in the main repo. However there are gaps: no architecture/design docs (the summary counts zero of them), only an unstructured 'Samples' section with no ordering and no headings, so the outline is visible but navigable content is missing, and the samples directory README omits a contributing/guidance note.

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ 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.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D22 · Internal API ConsistencyWeak◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Verified

2 API inconsistencies across 3 exposed types.

Inconsistent naming for retrieval operations. Permission and Feature controllers use 'GetAsync' for fetching by identifier/context, while Tenant controller uses 'GetAsync' for single entity and 'GetListAsync' for collections. More critically, the return types and parameter structures differ significantly between Permission/Feature (provider-based) and Tenant (ID-based), but the method names 'GetAsync' are overloaded with different semantic meanings (lookup by composite key vs lookup by ID). Additionally, Tenant has 'GetListAsync' while others lack a list endpoint, creating an asymmetry in CRUD surface area.

Inconsistent parameter structure for update operations. Permission and Feature controllers use a composite key (providerName, providerKey) for identification, while Tenant uses a simple ID string. This forces clients to handle different patterns for similar operations. Furthermore, the return types differ: Permission and Feature UpdateAsync return Task (void), while Tenant UpdateAsync returns ValueTask<TenantDto> (the updated entity). This inconsistency in return values makes it difficult to write generic client code or error handling.

What to do

Resolve the 1 Inconsistent naming for retrieval operations. Permission and Feature… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent parameter structure for update operations. Permission and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D23 · Boundary Type-Coupling9.6 / 10Stronggated by 7 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Verified

7 domain type(s) cross context boundaries across 21 contexts.

Cross-context type IMultiTenant (LinFx → LinFx.Extensions.AuditLogging) · ×4src/LinFx.Extensions.AuditLogging/Domain/AuditLog.cs:11

Cross-context type EntityChangeType (LinFx → LinFx.Extensions.AuditLogging) · ×3src/LinFx.Extensions.AuditLogging/Domain/EntityChange.cs:20

What to do

Resolve the 4 Cross-context type IMultiTenant (LinFx → LinFx.Extensions.AuditLogging) finding(s) in Boundary Type-Coupling — start with AuditLog.cs, AuditLogAction.cs, EntityChange.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Cross-context type EntityChangeType (LinFx →… finding(s) in Boundary Type-Coupling — start with IAuditLogRepository.cs (2), EntityChange.cs. — One of this dimension's main actionable groups (3 warning-level).
Stand up a CI pipeline, then gate Boundary Type-Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Documented

58 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion9.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 21 projects flagged as possibly oversized/incoherent.

Split LinFx

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D27 · Navigability7.0 / 10Adequate✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. 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.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Documented

66 % of calls cross a namespace and 18 % go through an interface, but 80 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Pass-through layer · ×2REDACTED:11

What to do

Resolve the 2 Pass-through layer finding(s) in Navigability — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).

Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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.

Do you agree with this assessment?

D29 · Static Analysis (SAST)5.6 / 10Adequate✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 5.6 / 10 · rule-coverage 100% · ceiling Documented

11 finding(s): 0 critical, 0 high, 11 medium, 0 low. semgrep hit a parse error in 110 file(s) — `samples/IdentityService.Host/Controllers/AccountController.cs` (line 17), `samples/IdentityService.Host/EntityFrameworkCore/ApplicationDbContext.cs` (line 8), `samples/IdentityService.Host/Extensions/ExceptionHandler.cs` (line 6), `samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs` (line 18), `src/LinFx.Extensions.AspNetCore.Authentication.WeChat/CachedPropertiesDataFormat.cs` (line 10), … (+105 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 110 of those file(s) — `samples/IdentityService.Host/Controllers/AccountController.cs`, `samples/IdentityService.Host/EntityFrameworkCore/ApplicationDbContext.cs`, `samples/IdentityService.Host/Extensions/ExceptionHandler.cs`, `samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs`, `src/LinFx.Extensions.AspNetCore.Authentication.WeChat/CachedPropertiesDataFormat.cs`, … (+105 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.

REDACTED

What to do

Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (10 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities4.8 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.8 / 10 · rule-coverage 100% · ceiling Documented

9 finding(s): 0 critical, 8 high, 1 medium, 0 low.

REDACTED

What to do

Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

129 of 129 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/LinFx/Extensions/Caching/DistributedCache.cs. Counted over 129 of the 832 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×126src/LinFx/Linq/AsyncQueryableExecuter.cs:1

Most significant orphaned file · ×3src/LinFx/Extensions/Caching/DistributedCache.cs:1

Dormant codebase

What to do

Resolve the 126 Orphaned file finding(s) in Knowledge Freshness — start with AsyncQueryableExecuter.cs, IDistributedCache.cs, REDACTED. — One of this dimension's main actionable groups (126 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with DistributedCache.cs, MongoDbRepository.cs, EfDbContext.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX10 · Code composition9.8 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

The namespaces LinFx.Extensions.ObjectExtending ↔ LinFx.Extensions.ObjectExtending.Modularity depend on each other. The lightest dependency in the cycle is LinFx.Extensions.ObjectExtending → LinFx.Extensions.ObjectExtending.Modularity (LinFx.Extensions.ObjectExtending.ModuleObjectExtensionManagerExtensions → LinFx.Extensions.ObjectExtending.Modularity.ModuleExtensionConfigurationDictionary, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/LinFx/Extensions/ObjectExtending/ModuleObjectExtensionManagerExtensions.cs:2
The namespaces LinFx ↔ LinFx.Domain.Entities.Events ↔ LinFx.Domain.Entities.Events.Distributed ↔ LinFx.Domain.Repositories ↔ LinFx.Domain.Repositories.MongoDB ↔ LinFx.Extensions.Auditing ↔ LinFx.Extensions.Data ↔ LinFx.Extensions.DependencyInjection ↔ LinFx.Extensions.DynamicProxy ↔ LinFx.Extensions.EntityFrameworkCore ↔ LinFx.Extensions.EntityFrameworkCore.DependencyInjection ↔ LinFx.Extensions.EntityFrameworkCore.EntityHistory ↔ LinFx.Extensions.EventBus ↔ LinFx.Extensions.EventBus.Distributed ↔ LinFx.Extensions.EventBus.Local ↔ LinFx.Extensions.Modularity ↔ LinFx.Extensions.MongoDB ↔ LinFx.Extensions.MongoDB.DependencyInjection ↔ LinFx.Extensions.MongoDB.MongoDB ↔ LinFx.Extensions.MultiTenancy ↔ LinFx.Extensions.Setting ↔ LinFx.Extensions.Threading ↔ LinFx.Extensions.Timing ↔ LinFx.Extensions.Uow ↔ LinFx.Security.Claims ↔ LinFx.Security.Users ↔ Microsoft.Extensions.DependencyInjection ↔ Volo.Abp.MongoDB depend on each other. The lightest dependency in the cycle is LinFx → LinFx.Extensions.DependencyInjection (LinFx.ApplicationInitializationContext → LinFx.Extensions.DependencyInjection.IServiceProviderAccessor, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/LinFx/ApplicationInitializationContext.cs:2
The namespaces LinFx.Extensions.AuditLogging ↔ LinFx.Extensions.AuditLogging.EntityFrameworkCore depend on each other. The lightest dependency in the cycle is LinFx.Extensions.AuditLogging → LinFx.Extensions.AuditLogging.EntityFrameworkCore (LinFx.Extensions.AuditLogging.AuditingStore → LinFx.Extensions.AuditLogging.EntityFrameworkCore.AuditLoggingDbContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/LinFx.Extensions.AuditLogging/Domain/AuditingStore.cs:2

What to do

Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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.

`IDistributedCache<TCacheItem, TCacheKey>` declares 20 members: `Get`, `GetMany`, `GetManyAsync`, `GetAsync`, `GetOrAdd`, `GetOrAddAsync`, `GetOrAddMany`, `GetOrAddManyAsync`, `Set`, `SetAsync`, `SetMany`, `SetManyAsync`, `Refresh`, `RefreshAsync`, `RefreshMany`, `RefreshManyAsync`, `Remove`, `RemoveAsync`, `RemoveMany`, `RemoveManyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/LinFx/Extensions/Caching/IDistributedCache.cs:19
`IUnitOfWork` declares 19 members: `Id`, `Items`, `Failed`, `Disposed`, `Options`, `Outer`, `IsReserved`, `IsDisposed`, `IsCompleted`, `ReservationName`, `SetOuter`, `Initialize`, `Reserve`, `SaveChangesAsync`, `CompleteAsync`, `RollbackAsync`, `OnCompleted`, `AddOrReplaceLocalEvent`, `AddOrReplaceDistributedEvent`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/LinFx/Extensions/Uow/IUnitOfWork.cs:8
`IAsyncQueryableExecuter` declares 66 members: `ContainsAsync`, `AnyAsync`, `AnyAsync`, `AllAsync`, `CountAsync`, `CountAsync`, `LongCountAsync`, `LongCountAsync`, `FirstAsync`, `FirstAsync`, `FirstOrDefaultAsync`, `FirstOrDefaultAsync`, `LastAsync`, `LastAsync`, `LastOrDefaultAsync`, `LastOrDefaultAsync`, `SingleAsync`, `SingleAsync`, `SingleOrDefaultAsync`, `SingleOrDefaultAsync`, `MinAsync`, `MinAsync`, `MaxAsync`, `MaxAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, and 26 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 66 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 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/LinFx/Linq/IAsyncQueryableExecuter.cs:6
`IAsyncQueryableProvider` declares 67 members: `CanExecute`, `ContainsAsync`, `AnyAsync`, `AnyAsync`, `AllAsync`, `CountAsync`, `CountAsync`, `LongCountAsync`, `LongCountAsync`, `FirstAsync`, `FirstAsync`, `FirstOrDefaultAsync`, `FirstOrDefaultAsync`, `LastAsync`, `LastAsync`, `LastOrDefaultAsync`, `LastOrDefaultAsync`, `SingleAsync`, `SingleAsync`, `SingleOrDefaultAsync`, `SingleOrDefaultAsync`, `MinAsync`, `MinAsync`, `MaxAsync`, `MaxAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, and 27 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 67 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/LinFx/Linq/IAsyncQueryableProvider.cs:6

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.

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.

Do you agree with this assessment?

C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

Do you agree with this assessment?

C3 · Audit Trail10.0 / 10Exemplary✓ Tool-verified

Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.

Method: Roslyn scan: audit-trail mechanism graded (SaveChanges interceptor/immutable AuditLog/[Audited] strong; bare IAuditable/AddAuditing weak). Deterministic.

Do you agree with this assessment?

ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

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?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

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. (×8) — src/LinFx/Extensions/ObjectExtending/ExtensibleObject.cs:27, src/LinFx/Extensions/Timing/TimingSettingProvider.cs:13, src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:475, …

What to do

Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs6.6 / 10Adequate✓ Tool-verified

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.

`GetMongoQueryableAsync` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:472 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:475
`GetEntityModel` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.MongoDB/MongoDbContext.cs:37 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/LinFx.Extensions.MongoDB/MongoDbContext.cs:39
`DeleteAsync` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.PermissionManagement/Application/PermissionManagementProvider.cs:70 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:155
`UpdateAsync` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:267 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:160
`L` is a shipped member whose body only throws — and it is REACHED: src/LinFx/Extensions/Timing/TimingSettingProvider.cs:10 references it (1 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/LinFx/Extensions/Timing/TimingSettingProvider.cs:13
`MvcOptionsExtensions` has 4 unfinished members out of 6 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:9
`AddConventions` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:20
`AddModelBinders` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:40
`AddMetadataProviders` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:47
`AddFormatters` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:59
`DeleteAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:150
`TrySetId` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/LinFx/Domain/Entities/EntityHelper.cs:205
`HandleExceptionAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/LinFx/Extensions/Caching/DistributedCache.cs:1353
`ShouldRetryAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/LinFx/Extensions/EventBus/Local/LocalEventErrorHandler.cs:33
`LoggerExtensions` has 2 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/LinFx/Extensions/Logging/LoggerExtensions.cs:5
`LogKnownProperties` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/LinFx/Extensions/Logging/LoggerExtensions.cs:16
`LogSelfLogging` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/LinFx/Extensions/Logging/LoggerExtensions.cs:46
`Validate` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/LinFx/Extensions/ObjectExtending/ExtensibleObject.cs:27
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×22) — src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:89, src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:90, src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:93, …

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.

Do you agree with this assessment?

M1 · Documentation (README)6.1 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 20 of 21 project(s) that lack one — worth up to 1.9 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.

Do you agree with this assessment?

M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

What to do

Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates0.0 / 10Critical✓ 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.

No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

Add a CI workflow that builds and runs the test suite on every push/PR.

Do you agree with this assessment?

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

What to do

Make types internal by default and expose only the deliberate public API — even for a small library, every public type is a stability contract.

Do you agree with this assessment?

P2 · Observability5.4 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

Only 10/21 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 21, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Run what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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.

Do you agree with this assessment?

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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.

The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.

What to do

Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.

Do you agree with this assessment?

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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?

PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).

Do you agree with this assessment?

PF2 · Allocation hygiene6.9 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

Raise allocation-aware density on the hot paths — currently 62 use(s) across 35,879 production line(s) (~1.7/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.

Do you agree with this assessment?

PF3 · Async & latency hygiene4.5 / 10Weak✓ Tool-verified

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.

1 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).
`.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:118
Only 3/467 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
`await AuthorizationService.CheckAsync(policyName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Application/Services/ApplicationService.cs:134
`await scope.ServiceProvider.GetRequiredService<IModuleManager>().InitializeModulesA...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/ApplicationBase.cs:73
`await scope.ServiceProvider .GetRequiredService<IModuleManager>() .ShutdownModulesA...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/ApplicationBase.cs:118
`await InitializeModulesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/LinFx/ApplicationWithExternalServiceProvider.cs:41, src/LinFx/ApplicationWithInternalServiceProvider.cs:37
`await tcs.Task` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Collections/Concurrent/AwaitableConcurrentQueue.cs:27
`await InsertAsync(entity, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:59
`await SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×4) — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:63, src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:84, src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:97, …
`await UpdateAsync(entity, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:80
`await DeleteAsync(entity, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:93
`await FindAsync(id, includeDetails, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:122
`await FindAsync(id, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:133
`await DeleteAsync(entity, autoSave, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:137
`await DeleteAsync(id, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:144
`await repository.AsyncExecuter.ContainsAsync(repository.Queryable, item, cancellati...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:16
`await repository.AsyncExecuter.AnyAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:26
`await repository.AsyncExecuter.AnyAsync(repository.Queryable, predicate, cancellati...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:33
`await repository.AsyncExecuter.AllAsync(repository.Queryable, predicate, cancellati...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:40
`await repository.AsyncExecuter.CountAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:50
`await repository.AsyncExecuter.CountAsync(repository.Queryable, predicate, cancella...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:56
`await repository.AsyncExecuter.LongCountAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:61
`await repository.AsyncExecuter.LongCountAsync(repository.Queryable, predicate, canc...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:68
`await repository.AsyncExecuter.FirstAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:77
`await repository.AsyncExecuter.FirstAsync(repository.Queryable, predicate, cancella...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:84
`await repository.AsyncExecuter.FirstOrDefaultAsync(repository.Queryable, cancellati...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:90
`await repository.AsyncExecuter.FirstOrDefaultAsync(repository.Queryable, predicate,...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:97
`await repository.AsyncExecuter.LastAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:107
`await repository.AsyncExecuter.LastAsync(repository.Queryable, predicate, cancellat...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:114
`await repository.AsyncExecuter.LastOrDefaultAsync(repository.Queryable, cancellatio...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:120
`await repository.AsyncExecuter.LastOrDefaultAsync(repository.Queryable, predicate, ...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:127
`await repository.AsyncExecuter.SingleAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:137
`await repository.AsyncExecuter.SingleAsync(repository.Queryable, predicate, cancell...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:144
`await repository.AsyncExecuter.SingleOrDefaultAsync(repository.Queryable, cancellat...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:150
`await repository.AsyncExecuter.SingleOrDefaultAsync(repository.Queryable, predicate...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:157

What to do

Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.

Do you agree with this assessment?

S1 · Web-Security Posture0.0 / 10Critical✓ Tool-verified

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.

MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. (×3) — REDACTED:69, REDACTED:83, src/LinFx/Utils/StringExtensions.cs:379
The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — src/LinFx/Extensions/Identity/JwtTokenOptions.cs:37
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. — src/LinFx/Security/Encryption/StringEncryptionService.cs:29
This encryption's initialisation vector is a compile-time constant, so every message encrypted under the same key gets the same IV. An IV is not a secret and does not have to be one — its whole job is to be DIFFERENT each time, so that encrypting the same plaintext twice does not produce the same ciphertext. Fix it and CBC becomes an equality oracle: the mode XORs the IV into the first plaintext block and chains from there, so two messages encrypted with the same key and IV produce byte-identical ciphertext for exactly as long as their plaintexts agree. An observer who can see two ciphertexts — a repository of encrypted config files, a database column, a backup — learns that two records match and how many blocks in they diverge, without the key and without breaking anything. The same defect under a counter-based mode is worse and not recoverable by comparison: CTR and GCM XOR the plaintext against a keystream determined by the key and nonce, so a repeated nonce leaks the XOR of the two plaintexts outright, and under GCM it also forfeits the authentication key. Generate the IV with a cryptographic RNG for each message — `RandomNumberGenerator.Fill(iv)` in .NET, `crypto.randomBytes(16)` in Node — and write it alongside the ciphertext (prepending the block is the usual spelling); the receiver reads it back from there. Deriving the IV from the key material is the specific trap to avoid: it looks like rigour and produces a constant, because the derivation's inputs do not change between messages. — REDACTED:16
This code fixes PBKDF2-SHA-1 at 1,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. (×2) — src/LinFx/Security/Encryption/StringEncryptionService.cs:25, src/LinFx/Security/Encryption/StringEncryptionService.cs:47
DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes. (×2) — REDACTED:235, REDACTED:258
`ValidateAudience`, `ValidateIssuer` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — samples/IdentityService.Host/Application.cs:59
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. — samples/IdentityService.Host/Program.cs:26
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. — samples/IdentityService.Host/Program.cs:26

What to do

Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `REDACTED:69` (MD5), `REDACTED:83` (MD5), `src/LinFx/Utils/StringExtensions.cs:379` (MD5). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
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.
Generate a fresh random IV for every encryption with `RandomNumberGenerator.Fill` and store or transmit it next to the ciphertext, rather than fixing it in the source or deriving it from the key material — a derived IV is constant, because its inputs do not vary between messages. An IV need not be secret, only unpredictable and unique per message; under CTR/GCM a repeated nonce is catastrophic rather than merely leaky.
Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 2 sites, not one: `src/LinFx/Security/Encryption/StringEncryptionService.cs:25` (PBKDF2-SHA-1, 1,000 iterations), `src/LinFx/Security/Encryption/StringEncryptionService.cs:47` (PBKDF2-SHA-1, 1,000 iterations). 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: `REDACTED:235` (RijndaelManaged), `REDACTED:258` (RijndaelManaged). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.

Do you agree with this assessment?

X1 · Async correctness7.6 / 10Strong✓ Tool-verified

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.

Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×3) — src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:456, src/LinFx.Extensions.EntityFrameworkCore/DependencyInjection/DbContextOptionsFactory.cs:120, src/LinFx.Extensions.EntityFrameworkCore/DependencyInjection/DbContextOptionsFactory.cs:124
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. — src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:118

What to do

Sync-over-async (deadlock risk) through `.Result`

Do you agree with this assessment?

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X18 · Disposal-pattern correctness4.7 / 10Weak✓ Tool-verified

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.

`cng` is a `RSACng`, which implements `IDisposable`, and it is created here (line 20). Every use of it in `CreateRsaSecurityKey` 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 cng = …;`), which releases it at the end of the scope on every path including a throw. — src/LinFx/Utils/CryptoUtils.cs:20
`reader` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 10). Every use of it in `ReadCsvStream` 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 reader = …;`), which releases it at the end of the scope on every path including a throw. — src/LinFx/Utils/CsvConverter.cs:10
`stringWriter` is a `StringWriter`, which implements `IDisposable`, and it is created here (line 50). Every use of it in `ExportCsv` 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 stringWriter = …;`), which releases it at the end of the scope on every path including a throw. — src/LinFx/Utils/CsvConverter.cs:50
`DCSP` is a `Aes`, which implements `IDisposable`, and it is created here (line 29). Every use of it in `DESEncode` 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 DCSP = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:29
`cStream` is a `CryptoStream`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `DESEncode` 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 cStream = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:31
`DCSP` is a `Aes`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `DESDecrypt` 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 DCSP = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:49
`cStream` is a `CryptoStream`, which implements `IDisposable`, and it is created here (line 51). Every use of it in `DESDecrypt` 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 cStream = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:51
`rm` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 235). Every use of it in `AESEncrypt` 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 rm = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:235
`rm` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 258). Every use of it in `AESDecrypt` 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 rm = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:258
`rDel` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 281). Every use of it in `Encrypt` 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 rDel = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:281
`rDel` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 303). Every use of it in `Decrypt` 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 rDel = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:303
`SessionHandle` is never created by `MongoDbTransactionApi` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 27). Its declared type `IClientSessionHandle` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/LinFx.Extensions.MongoDB/Uow/MongoDB/MongoDbTransactionApi.cs:27
`Channel` is never created by `ChannelPoolItem` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 143). Its declared type `IModel` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/LinFx.Extensions.RabbitMQ/ChannelPool.cs:143

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.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X2 · Cancellation propagation6.5 / 10Adequate✓ Tool-verified

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 107/254 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/LinFx/Application/Services/ApplicationService.cs:129, src/LinFx/ApplicationBase.cs:70, src/LinFx/ApplicationBase.cs:115, …

What to do

Thread a CancellationToken through async methods so work stops promptly on cancellation.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation5.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

`LogDebug` at line 102 is called with an argument built by `string.Join(",", cacheKeys)` (line 102), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:102
`LogDebug` at line 107 is called with an argument built by `string.Join(",", cacheKeys)` (line 107), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:107
`LogDebug` at line 113 is called with an argument built by `string.Join(",", notCacheKeys)` (line 113), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:113

What to do

Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X3 · Exception handling5.2 / 10Adequate✓ Tool-verified

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.

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — src/LinFx/Extensions/ObjectMapping/DefaultObjectMapper.cs:62, src/LinFx/Extensions/Uow/UnitOfWork.cs:277, src/LinFx/Extensions/Uow/UnitOfWork.cs:297, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×5) — src/LinFx.Extensions.Kafka/ConsumerPool.cs:78, src/LinFx.Extensions.Kafka/KafkaMessageConsumer.cs:162, src/LinFx.Extensions.Kafka/ProducerPool.cs:81, …

What to do

Swallowed exception (empty catch)

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.

Do you agree with this assessment?

X4 · Structured logging3.5 / 10Weak✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×29) — src/LinFx/Extensions/Logging/LoggerExtensions.cs:10, src/LinFx/Extensions/Modularity/ModuleHelper.cs:41, src/LinFx.Extensions.Kafka/ConsumerPool.cs:64, …

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types9.1 / 10Exemplary✓ Tool-verified

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.

19/21 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~0.2 `!` suppressions per 1k syntax nodes — 22 suppression(s) across the 137668 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.

Lens	Score	Rating	Impact
Code Health	53%	Adequate — gated by D18, X4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	97%	Exemplary	Solid.
Maturity	39%	Weak — gated by D34, M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	17%	Critical — gated by D8, D9, D12, D13, P1, P3, P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	46%	Weak — gated by C1, S1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven	100%	Exemplary	Strongest area.
Performance	56%	Adequate	Acceptable, with room to improve.

Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 13 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 — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 37 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.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
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 — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'LinFx.Extensions.FeatureManagement.HttpApi.csproj'`: Unable to proceed with project 'src/LinFx.Extensions.FeatureManagement.HttpApi/LinFx.Extensions.FeatureManagement.HttpApi.csproj'. Ensure you have…; runtime evidence skipped (launch chosen because src/LinFx.Extensions.FeatureManagement.HttpApi/LinFx.Extensions.FeatureManagement.HttpApi.csproj is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 106 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the target did not build
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).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 14 aggregate root(s) (AggregateRoot/IAggregateRoot); its 11 aggregate(s) are building blocks, test types or a library's examples — not the repository's own domain; a Domain/Aggregates/ValueObjects layer; 1 repository port(s) loading or saving an aggregate/entity; a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level samples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
ED3 Event naming — no domain or integration events detected — event-naming check not applicable
ED4 Outbox / dual-write — no persistence writes or publishes observed in handlers — atomicity not assessable
ED5 Idempotency — 4 mutating command handler(s)/consumer(s) detected and 2 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 — no CI workflow found
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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.

Critical — 40 finding(s)

D17 · Explicit Debt · EmptyCatchBlock · ×11

EmptyCatchBlock src/LinFx.Extensions.Kafka/ConsumerPool.cs:78 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx.Extensions.Kafka/KafkaMessageConsumer.cs:162 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx.Extensions.Kafka/ProducerPool.cs:81 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx.Extensions.RabbitMQ/ChannelPool.cs:73 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx.Extensions.RabbitMQ/ConnectionPool.cs:51 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:161 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx/Extensions/ObjectMapping/DefaultObjectMapper.cs:62 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx/Extensions/Uow/UnitOfWork.cs:277 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx/Extensions/Uow/UnitOfWork.cs:297 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx/Extensions/Uow/UnitOfWork.cs:309 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/LinFx/Reflection/TypeFinder.cs:35 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.

D30 · Dependency Vulnerabilities · High CVE · ×8

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

IC1 · Incompleteness & stubs · Unfinished stub · ×5

Unfinished stub — throws NotImplementedException src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:475 — `GetMongoQueryableAsync` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:472 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.MongoDB/MongoDbContext.cs:39 — `GetEntityModel` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.MongoDB/MongoDbContext.cs:37 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:155 — `DeleteAsync` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.PermissionManagement/Application/PermissionManagementProvider.cs:70 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:160 — `UpdateAsync` is a shipped member whose body only throws — and it is REACHED: src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:267 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException src/LinFx/Extensions/Timing/TimingSettingProvider.cs:13 — `L` is a shipped member whose body only throws — and it is REACHED: src/LinFx/Extensions/Timing/TimingSettingProvider.cs:10 references it (1 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.

AX3 · Project dependency cycles · Namespace dependency cycle · ×3

Namespace dependency cycle src/LinFx/Extensions/ObjectExtending/ModuleObjectExtensionManagerExtensions.cs:2 — The namespaces LinFx.Extensions.ObjectExtending ↔ LinFx.Extensions.ObjectExtending.Modularity depend on each other. The lightest dependency in the cycle is LinFx.Extensions.ObjectExtending → LinFx.Extensions.ObjectExtending.Modularity (LinFx.Extensions.ObjectExtending.ModuleObjectExtensionManagerExtensions → LinFx.Extensions.ObjectExtending.Modularity.ModuleExtensionConfigurationDictionary, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/LinFx/ApplicationInitializationContext.cs:2 — The namespaces LinFx ↔ LinFx.Domain.Entities.Events ↔ LinFx.Domain.Entities.Events.Distributed ↔ LinFx.Domain.Repositories ↔ LinFx.Domain.Repositories.MongoDB ↔ LinFx.Extensions.Auditing ↔ LinFx.Extensions.Data ↔ LinFx.Extensions.DependencyInjection ↔ LinFx.Extensions.DynamicProxy ↔ LinFx.Extensions.EntityFrameworkCore ↔ LinFx.Extensions.EntityFrameworkCore.DependencyInjection ↔ LinFx.Extensions.EntityFrameworkCore.EntityHistory ↔ LinFx.Extensions.EventBus ↔ LinFx.Extensions.EventBus.Distributed ↔ LinFx.Extensions.EventBus.Local ↔ LinFx.Extensions.Modularity ↔ LinFx.Extensions.MongoDB ↔ LinFx.Extensions.MongoDB.DependencyInjection ↔ LinFx.Extensions.MongoDB.MongoDB ↔ LinFx.Extensions.MultiTenancy ↔ LinFx.Extensions.Setting ↔ LinFx.Extensions.Threading ↔ LinFx.Extensions.Timing ↔ LinFx.Extensions.Uow ↔ LinFx.Security.Claims ↔ LinFx.Security.Users ↔ Microsoft.Extensions.DependencyInjection ↔ Volo.Abp.MongoDB depend on each other. The lightest dependency in the cycle is LinFx → LinFx.Extensions.DependencyInjection (LinFx.ApplicationInitializationContext → LinFx.Extensions.DependencyInjection.IServiceProviderAccessor, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/LinFx.Extensions.AuditLogging/Domain/AuditingStore.cs:2 — The namespaces LinFx.Extensions.AuditLogging ↔ LinFx.Extensions.AuditLogging.EntityFrameworkCore depend on each other. The lightest dependency in the cycle is LinFx.Extensions.AuditLogging → LinFx.Extensions.AuditLogging.EntityFrameworkCore (LinFx.Extensions.AuditLogging.AuditingStore → LinFx.Extensions.AuditLogging.EntityFrameworkCore.AuditLoggingDbContext, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.

D17 · Explicit Debt · NoWarnInCsproj · ×3

NoWarnInCsproj common.props:6 — 1701 — 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.
NoWarnInCsproj common.props:6 — 1702 — 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.
NoWarnInCsproj common.props:6 — 1591 — 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.

D12 · Dependency Hygiene · Vulnerable · ×2

Vulnerable: Microsoft.Extensions.Caching.Memory — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: System.Text.Json — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]

D13 · REDACTED Scanning · Leaked secret · ×2

REDACTED
REDACTED

D17 · Explicit Debt · WriteOnlyPrivateField · ×2

WriteOnlyPrivateField src/LinFx.Extensions.AspNetCore.Authentication.WeChat/CachedPropertiesDataFormat.cs:15 — private IDataProtector _dataProtector — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/LinFx/Extensions/Authorization/AuthorizationPolicyProvider.cs:16 — private AuthorizationOptions _options — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.

D17 · Explicit Debt · FileScopedPragmaDisable · ×1

FileScopedPragmaDisable src/LinFx.Extensions.EntityFrameworkCore/DependencyInjection/DbContextOptionsFactory.cs:111 — #pragma warning disable 618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.

D28 · Secrets (history) · REDACTED · ×1

REDACTED

D8 · Code Coverage · No automated tests · ×1

No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.

S1 · Web-Security Posture · Cryptographic key material is a compile-time constant · ×1

Cryptographic key material is a compile-time constant src/LinFx/Extensions/Identity/JwtTokenOptions.cs:37 — The value is the token-signing key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.

Serious — 540 finding(s)

D17 · Explicit Debt · Dead code · ×173

Dead code: PagedFilterResultRequest src/LinFx/Application/Dtos/PagedFilterResultRequest.cs:8 — NamedType PagedFilterResultRequest — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: AwaitableConcurrentQueue src/LinFx/Collections/Concurrent/AwaitableConcurrentQueue.cs:5 — NamedType AwaitableConcurrentQueue — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: AsNameValueCollection src/LinFx/Collections/IReadableStringCollectionExtensions.cs:9 — Method AsNameValueCollection — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: AsNameValueCollection src/LinFx/Collections/IReadableStringCollectionExtensions.cs:22 — Method AsNameValueCollection — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: SelectTry src/LinFx/Collections/LinqSelectExtensions.cs:5 — Method SelectTry — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: OnCaughtException src/LinFx/Collections/LinqSelectExtensions.cs:22 — Method OnCaughtException — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: OnCaughtException src/LinFx/Collections/LinqSelectExtensions.cs:24 — Method OnCaughtException — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: AddRepository src/LinFx/Domain/DependencyInjection/ICommonDbContextRegistrationOptionsBuilder.cs:59 — Method AddRepository — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: SetDefaultRepositoryClasses src/LinFx/Domain/DependencyInjection/ICommonDbContextRegistrationOptionsBuilder.cs:67 — Method SetDefaultRepositoryClasses — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: FullAuditedAggregateRoot src/LinFx/Domain/Entities/Auditing/FullAuditedAggregateRoot.cs:9 — NamedType FullAuditedAggregateRoot — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: FullAuditedEntity src/LinFx/Domain/Entities/Auditing/FullAuditedEntity.cs:9 — NamedType FullAuditedEntity — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: FullAuditedEntity src/LinFx/Domain/Entities/Auditing/FullAuditedEntity.cs:26 — NamedType FullAuditedEntity — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: IsEntityWithId src/LinFx/Domain/Entities/EntityHelper.cs:106 — Method IsEntityWithId — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: HasDefaultId src/LinFx/Domain/Entities/EntityHelper.cs:117 — Method HasDefaultId — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: IsDefaultKeyValue src/LinFx/Domain/Entities/EntityHelper.cs:132 — Method IsDefaultKeyValue — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: CreateEqualityExpressionForId src/LinFx/Domain/Entities/EntityHelper.cs:188 — Method CreateEqualityExpressionForId — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: AddNamespace src/LinFx/Domain/Entities/Events/Distributed/AutoEntityDistributedEventSelectorListExtensions.cs:10 — Method AddNamespace — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: AddAll src/LinFx/Domain/Entities/Events/Distributed/AutoEntityDistributedEventSelectorListExtensions.cs:53 — Method AddAll — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: IExtendableObject src/LinFx/Domain/Entities/IExtendableObject.cs:6 — NamedType IExtendableObject — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: BasicRepositoryBase src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:111 — NamedType BasicRepositoryBase — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: GetCountAsync src/LinFx/Domain/Repositories/IReadOnlyBasicRepository.cs:19 — Method GetCountAsync — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: GetPagedListAsync src/LinFx/Domain/Repositories/IReadOnlyBasicRepository.cs:30 — Method GetPagedListAsync — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: WithDetailsAsync src/LinFx/Domain/Repositories/IReadOnlyRepository.cs:12 — Method WithDetailsAsync — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: WithDetailsAsync src/LinFx/Domain/Repositories/IReadOnlyRepository.cs:15 — Method WithDetailsAsync — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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: ISupportsExplicitLoading src/LinFx/Domain/Repositories/ISupportsExplicitLoading.cs:6 — NamedType ISupportsExplicitLoading — Roslyn's SymbolFinder walked every project the solution loads, including LinFx, 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.
+ 148 more in this group — see findings.md.

D17 · Explicit Debt · CommentedOutCode · ×83

CommentedOutCode samples/IdentityService.Host/Application.cs:47 — 4 consecutive commented-code lines
CommentedOutCode samples/IdentityService.Host/Application.cs:68 — 4 consecutive commented-code lines
CommentedOutCode samples/IdentityService.Host/Extensions/ExceptionHandler.cs:22 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.AspNetCore/Auditing/AspNetCoreAuditLogContributor.cs:35 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.AspNetCore/Mvc/AspNetCoreMvcModule.cs:70 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.AspNetCore/Mvc/AspNetCoreMvcModule.cs:92 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.AspNetCore/Mvc/AspNetCoreMvcModule.cs:163 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.EntityFrameworkCore/EfDbContext.cs:399 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.EntityFrameworkCore/Modeling/ModelBuilderExtensions.cs:34 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.EntityFrameworkCore/Modeling/ModelBuilderExtensions.cs:43 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.EntityFrameworkCore/Modeling/ModelBuilderExtensions.cs:52 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.EntityFrameworkCore/Modeling/ModelBuilderExtensions.cs:61 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:100 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs:109 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.FeatureManagement/EntityFrameworkCore/FeatureManagementDbContextModelBuilderExtensions.cs:19 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx.Extensions.TenantManagement/EntityFrameworkCore/TenantManagementDbContextModelCreatingExtensions.cs:11 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Domain/Entities/EntityHelper.cs:56 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Domain/Entities/EntityHelper.cs:84 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Domain/Entities/ExtendableObjectExtensions.cs:32 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Domain/Entities/ExtendableObjectExtensions.cs:37 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Extensions/DependencyInjection/ServiceCollectionCommonExtensions.cs:117 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Extensions/DependencyInjection/ServiceCollectionCommonExtensions.cs:126 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Extensions/DependencyInjection/ServiceCollectionCommonExtensions.cs:135 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Extensions/DependencyInjection/ServiceCollectionCommonExtensions.cs:144 — 4 consecutive commented-code lines
CommentedOutCode src/LinFx/Extensions/EventBus/Distributed/DistributedEventBusBase.cs:43 — 4 consecutive commented-code lines
+ 58 more in this group — see findings.md.

D17 · Explicit Debt · TodoComment · ×54

TodoComment src/LinFx.Extensions.AspNetCore/Auditing/AspNetCoreAuditLogContributor.cs:40 — //TODO: context.AuditInfo.ClientName — 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/LinFx.Extensions.AspNetCore/Auditing/AspNetCoreAuditLogContributor.cs:55 — //TODO: Add options to include/exclude query, schema and host — 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/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultHttpExceptionStatusCodeFinder.cs:33 — //TODO: Handle SecurityException..? — 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/LinFx.Extensions.AspNetCore/ExceptionHandling/ExceptionHandlingMiddleware.cs:39 — //TODO: Align with ExceptionFilter.ShouldHandleException! — 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/LinFx.Extensions.AspNetCore/Mvc/AspNetCoreMvcModule.cs:101 — //.AddViewLocalization(); //TODO: How to configure from the application? Also, consider to move to a UI module since APIs does not care about it. — 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/LinFx.Extensions.AspNetCore/Mvc/AspNetCoreMvcModule.cs:116 — //TODO: AddViewLocalization by default..? — 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/LinFx.Extensions.AspNetCore/Mvc/Auditing/AuditActionFilter.cs:24 — //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/LinFx.Extensions.AspNetCore/Mvc/ExceptionHandling/ExceptionFilter.cs:41 — //TODO: Create DontWrap attribute to control wrapping..? — 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/LinFx.Extensions.AspNetCore/Mvc/ExceptionHandling/ExceptionFilter.cs:62 — //TODO: Trigger an ExceptionHandled event or something like that. — 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/LinFx.Extensions.Autofac/Autofac/Extensions/DependencyInjection/AutofacRegistration.cs:176 — //TODO: ConfigureConventions ? — 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/LinFx.Extensions.EntityFrameworkCore/Modeling/EntityTypeBuilderExtensions.cs:297 — //TODO: Add other interfaces (IAuditedObject<TUser>...) — 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/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:17 — /* TODO: How to handle unsubscribe to unbind on RabbitMq (may not be possible for) — 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/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:30 — //TODO: Accessing to the List<IEventHandlerFactory> may not be thread-safe! — 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/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:121 — //TODO: Multi-threading! — 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/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:359 — //TODO: Support inheritance? But it does not support on subscription to RabbitMq! — 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/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs:34 — //TODO: Instead, use IServiceScopeFactory and create a scope..? — 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/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs:159 — //TODO: Fallback is not used — 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/LinFx.Extensions.FeatureManagement/Domain/IFeatureManagementProvider.cs:10 — //TODO: Other better method name. — 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/LinFx.Extensions.FeatureManagement/Domain/IFeatureManagementProvider.cs:13 — //TODO: Other better method name. — 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/LinFx.Extensions.MongoDB/Uow/MongoDB/UnitOfWorkMongoDbContextProvider.cs:59 — //TODO: Create only single MongoDbClient per connection string in an application (extract MongoClientCache for example). — 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/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:241 — // //TODO: BusinessException — 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/LinFx.Extensions.PermissionManagement/PermissionManagementModule.cs:25 — //TODO: Can we prevent duplication of permission names without breaking the design and making the system complicated — 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/LinFx.Extensions.SettingManagement/Domain/SettingManagementProvider.cs:10 — //TODO: Rename to Store — 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/LinFx.Extensions.SettingManagement/Domain/SettingManagementStore.cs:207 — //TODO: throw ex when name is null? — 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/LinFx.Extensions.SettingManagement/Domain/SettingManager.cs:30 — //TODO: Instead, use IHybridServiceScopeFactory and create a scope..? — 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.
+ 29 more in this group — see findings.md.

X2 · Cancellation propagation · Async method without CancellationToken · ×39

Async method without CancellationToken: CheckPolicyAsync src/LinFx/Application/Services/ApplicationService.cs:129 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeModulesAsync src/LinFx/ApplicationBase.cs:70 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShutdownAsync src/LinFx/ApplicationBase.cs:115 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeAsync src/LinFx/ApplicationWithExternalServiceProvider.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeAsync src/LinFx/ApplicationWithInternalServiceProvider.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WithDetailsAsync src/LinFx/Domain/Repositories/RepositoryBase.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InterceptAsync src/LinFx/Extensions/Auditing/AuditingInterceptor.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ProceedByLoggingAsync src/LinFx/Extensions/Auditing/AuditingInterceptor.cs:65 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ProcessWithNewAuditingScopeAsync src/LinFx/Extensions/Auditing/AuditingInterceptor.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAsync src/LinFx/Extensions/Auditing/AuditingManager.cs:113 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAsync src/LinFx/Extensions/Auditing/AuditingManager.cs:139 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InterceptAsync src/LinFx/Extensions/Authorization/AuthorizationInterceptor.cs:12 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AuthorizeAsync src/LinFx/Extensions/Authorization/AuthorizationServiceExtensions.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsGrantedAsync src/LinFx/Extensions/Authorization/AuthorizationServiceExtensions.cs:18 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsGrantedAsync src/LinFx/Extensions/Authorization/AuthorizationServiceExtensions.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsGrantedAsync src/LinFx/Extensions/Authorization/AuthorizationServiceExtensions.cs:28 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckAsync src/LinFx/Extensions/Authorization/AuthorizationServiceExtensions.cs:37 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckAsync src/LinFx/Extensions/Authorization/AuthorizationServiceExtensions.cs:49 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckAsync src/LinFx/Extensions/Authorization/MethodInvocationAuthorizationService.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckAsync src/LinFx/Extensions/Authorization/Permissions/ClientPermissionValueProvider.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsGrantedAsync src/LinFx/Extensions/Authorization/Permissions/PermissionChecker.cs:57 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsGrantedAsync src/LinFx/Extensions/Authorization/Permissions/PermissionCheckerExtensions.cs:7 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsGrantedAsync src/LinFx/Extensions/Authorization/Permissions/PermissionCheckerExtensions.cs:9 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckAsync src/LinFx/Extensions/Authorization/Permissions/RolePermissionValueProvider.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckAsync src/LinFx/Extensions/Authorization/Permissions/UserPermissionValueProvider.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
+ 14 more in this group — see findings.md.

PF3 · Async & latency hygiene · Awaits without ConfigureAwait(false) · ×38

Awaits without ConfigureAwait(false) — Only 3/467 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
Awaits without ConfigureAwait(false) src/LinFx/Application/Services/ApplicationService.cs:134 — `await AuthorizationService.CheckAsync(policyName)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/ApplicationBase.cs:73 — `await scope.ServiceProvider.GetRequiredService<IModuleManager>().InitializeModulesA...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/ApplicationBase.cs:118 — `await scope.ServiceProvider .GetRequiredService<IModuleManager>() .ShutdownModulesA...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/ApplicationWithExternalServiceProvider.cs:41 — `await InitializeModulesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/ApplicationWithInternalServiceProvider.cs:37 — `await InitializeModulesAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Collections/Concurrent/AwaitableConcurrentQueue.cs:27 — `await tcs.Task` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:59 — `await InsertAsync(entity, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:63 — `await SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:80 — `await UpdateAsync(entity, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:84 — `await SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:93 — `await DeleteAsync(entity, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:97 — `await SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:122 — `await FindAsync(id, includeDetails, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:133 — `await FindAsync(id, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:137 — `await DeleteAsync(entity, autoSave, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:144 — `await DeleteAsync(id, cancellationToken: cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:149 — `await SaveChangesAsync(cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:16 — `await repository.AsyncExecuter.ContainsAsync(repository.Queryable, item, cancellati...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:26 — `await repository.AsyncExecuter.AnyAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:33 — `await repository.AsyncExecuter.AnyAsync(repository.Queryable, predicate, cancellati...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:40 — `await repository.AsyncExecuter.AllAsync(repository.Queryable, predicate, cancellati...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:50 — `await repository.AsyncExecuter.CountAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:56 — `await repository.AsyncExecuter.CountAsync(repository.Queryable, predicate, cancella...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:61 — `await repository.AsyncExecuter.LongCountAsync(repository.Queryable, cancellationToken)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
+ 13 more in this group — see findings.md.

D17 · Explicit Debt · Whole file has no live code · ×12

Whole file has no live code — 2 debt markers inside it src/LinFx.Extensions.AspNetCore/Mvc/ModelBinding/DateTimeModelBinderProvider.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (2 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 2 debt markers inside it src/LinFx.Extensions.FeatureManagement/Domain/FeatureStore.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (2 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it src/LinFx.Extensions.MongoDB/DistributedEvents/IMongoDbContextEventInbox.cs:3 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it src/LinFx.Extensions.MongoDB/DistributedEvents/IMongoDbContextEventOutbox.cs:5 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 3 debt markers inside it src/LinFx.Extensions.MongoDB/DistributedEvents/IncomingEventRecord.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 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.)
Whole file has no live code — 7 debt markers inside it src/LinFx.Extensions.MongoDB/DistributedEvents/MongoDbContextEventInbox.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 7 debt markers (7 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 7 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 4 debt markers inside it src/LinFx.Extensions.MongoDB/DistributedEvents/MongoDbContextEventOutbox.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 4 debt markers (4 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 4 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 2 debt markers inside it src/LinFx.Extensions.MongoDB/DistributedEvents/OutgoingEventRecord.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 2 debt markers (2 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 2 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it src/LinFx.Extensions.SettingManagement/EntityFrameworkCore/SettingManagementEntityFrameworkCoreModule.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 12 debt markers inside it src/LinFx/Extensions/ObjectExtending/ExtensibleObjectValidator.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 12 debt markers (12 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 12 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 1 debt marker inside it src/LinFx/Extensions/ObjectExtending/Modularity/ExtensionPropertyConfigurationExtensions.cs:25 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 1 debt marker (1 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 1 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)
Whole file has no live code — 4 debt markers inside it src/LinFx/Extensions/Timing/TZConvertTimezoneProvider.cs:1 — Every line in this file is a comment or blank — it declares no type, member, using or attribute, so nothing in it reaches the build. Its 4 debt markers (4 CommentedOutCode) all sit inside that dead text: one decision to leave the whole file switched off, not 4 independent debts. It records no note anywhere: the file is switched off with nothing in it saying why, so a reader cannot tell whether it is waiting on something or was simply abandoned — which is the harder of the two to bring back. Decide the FILE rather than its lines — restore it, or delete it and let version control hold the history. (Every occurrence still counts toward the score and metrics.)

X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×11

Disposable created and abandoned in the method that made it src/LinFx/Utils/CryptoUtils.cs:20 — `cng` is a `RSACng`, which implements `IDisposable`, and it is created here (line 20). Every use of it in `CreateRsaSecurityKey` 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 cng = …;`), 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/LinFx/Utils/CsvConverter.cs:10 — `reader` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 10). Every use of it in `ReadCsvStream` 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 reader = …;`), 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/LinFx/Utils/CsvConverter.cs:50 — `stringWriter` is a `StringWriter`, which implements `IDisposable`, and it is created here (line 50). Every use of it in `ExportCsv` 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 stringWriter = …;`), 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 REDACTED:29 — `DCSP` is a `Aes`, which implements `IDisposable`, and it is created here (line 29). Every use of it in `DESEncode` 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 DCSP = …;`), 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 REDACTED:31 — `cStream` is a `CryptoStream`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `DESEncode` 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 cStream = …;`), 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 REDACTED:49 — `DCSP` is a `Aes`, which implements `IDisposable`, and it is created here (line 49). Every use of it in `DESDecrypt` 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 DCSP = …;`), 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 REDACTED:51 — `cStream` is a `CryptoStream`, which implements `IDisposable`, and it is created here (line 51). Every use of it in `DESDecrypt` 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 cStream = …;`), 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 REDACTED:235 — `rm` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 235). Every use of it in `AESEncrypt` 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 rm = …;`), 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 REDACTED:258 — `rm` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 258). Every use of it in `AESDecrypt` 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 rm = …;`), 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 REDACTED:281 — `rDel` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 281). Every use of it in `Encrypt` 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 rDel = …;`), 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 REDACTED:303 — `rDel` is a `RijndaelManaged`, which implements `IDisposable`, and it is created here (line 303). Every use of it in `Decrypt` 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 rDel = …;`), which releases it at the end of the scope on every path including a throw.

X3 · Exception handling · Swallowed exception (empty catch) · ×11

Swallowed exception (empty catch) src/LinFx/Extensions/ObjectMapping/DefaultObjectMapper.cs:62 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/LinFx/Extensions/Uow/UnitOfWork.cs:277 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/LinFx/Extensions/Uow/UnitOfWork.cs:297 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/LinFx/Extensions/Uow/UnitOfWork.cs:309 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/LinFx/Reflection/TypeFinder.cs:35 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/LinFx.Extensions.Kafka/ConsumerPool.cs:78 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/LinFx.Extensions.Kafka/KafkaMessageConsumer.cs:162 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/LinFx.Extensions.Kafka/ProducerPool.cs:81 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/LinFx.Extensions.RabbitMQ/ChannelPool.cs:73 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/LinFx.Extensions.RabbitMQ/ConnectionPool.cs:51 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:161 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

GD1 · Unfinished & placeholder code · Unfinished stub · ×8

Unfinished stub — throws NotImplementedException src/LinFx/Extensions/ObjectExtending/ExtensibleObject.cs:27 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/LinFx/Extensions/Timing/TimingSettingProvider.cs:13 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:475 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.MongoDB/MongoDbContext.cs:39 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.FeatureManagement/Domain/FeatureManagementStore.cs:41 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:150 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:155 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:160 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

IC1 · Incompleteness & stubs · Empty method body · ×7

Empty method body — does nothing with its inputs src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:20 — `AddConventions` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:40 — `AddModelBinders` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:47 — `AddMetadataProviders` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:59 — `AddFormatters` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/LinFx/Domain/Entities/EntityHelper.cs:205 — `TrySetId` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/LinFx/Extensions/Logging/LoggerExtensions.cs:16 — `LogKnownProperties` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/LinFx/Extensions/Logging/LoggerExtensions.cs:46 — `LogSelfLogging` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.

D3 · God Classes · TooManyMethods · ×5

TooManyMethods: AsyncQueryableExecuter src/LinFx/Linq/AsyncQueryableExecuter.cs — TooManyMethods — 338 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 30 methods; this is 38 over it, 2.27× 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: MongoDbAsyncQueryableProvider src/LinFx.Extensions.MongoDB/MongoDbAsyncQueryableProvider.cs — TooManyMethods — 139 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: MongoDbRepository src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs — TooManyMethods — 337 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: DistributedCache src/LinFx/Extensions/Caching/DistributedCache.cs — TooManyMethods — 656 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: EfDbContext src/LinFx.Extensions.EntityFrameworkCore/EfDbContext.cs — TooManyMethods — 261 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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.

D23 · Boundary Type-Coupling · Cross-context type IMultiTenant (LinFx → LinFx.Extensions.AuditLogging) · ×4

Cross-context type IMultiTenant (LinFx → LinFx.Extensions.AuditLogging) src/LinFx.Extensions.AuditLogging/Domain/AuditLog.cs:11 — IMultiTenant (context LinFx) is exposed in LinFx.Extensions.AuditLogging's public surface via AuditLog.IMultiTenant — couples the contexts.
Cross-context type IMultiTenant (LinFx → LinFx.Extensions.AuditLogging) src/LinFx.Extensions.AuditLogging/Domain/AuditLogAction.cs:11 — IMultiTenant (context LinFx) is exposed in LinFx.Extensions.AuditLogging's public surface via AuditLogAction.IMultiTenant — couples the contexts.
Cross-context type IMultiTenant (LinFx → LinFx.Extensions.AuditLogging) src/LinFx.Extensions.AuditLogging/Domain/EntityChange.cs:12 — IMultiTenant (context LinFx) is exposed in LinFx.Extensions.AuditLogging's public surface via EntityChange.IMultiTenant — couples the contexts.
Cross-context type IMultiTenant (LinFx → LinFx.Extensions.AuditLogging) src/LinFx.Extensions.AuditLogging/Domain/EntityPropertyChange.cs:11 — IMultiTenant (context LinFx) is exposed in LinFx.Extensions.AuditLogging's public surface via EntityPropertyChange.IMultiTenant — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type EntityChangeType (LinFx → LinFx.Extensions.AuditLogging) · ×3

Cross-context type EntityChangeType (LinFx → LinFx.Extensions.AuditLogging) src/LinFx.Extensions.AuditLogging/Domain/EntityChange.cs:20 — EntityChangeType (context LinFx) is exposed in LinFx.Extensions.AuditLogging's public surface via EntityChange.ChangeType — couples the contexts.
Cross-context type EntityChangeType (LinFx → LinFx.Extensions.AuditLogging) src/LinFx.Extensions.AuditLogging/Domain/IAuditLogRepository.cs:62 — EntityChangeType (context LinFx) is exposed in LinFx.Extensions.AuditLogging's public surface via IAuditLogRepository.GetEntityChangeListAsync — couples the contexts.
Cross-context type EntityChangeType (LinFx → LinFx.Extensions.AuditLogging) src/LinFx.Extensions.AuditLogging/Domain/IAuditLogRepository.cs:72 — EntityChangeType (context LinFx) is exposed in LinFx.Extensions.AuditLogging's public surface via IAuditLogRepository.GetEntityChangeCountAsync — couples the contexts.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3

Duplicated block (13 lines × 2) src/LinFx/Extensions/Caching/DistributedCache.cs:1259 — src/LinFx/Extensions/Caching/DistributedCache.cs:1259-1271 | src/LinFx/Extensions/Caching/DistributedCache.cs:1319-1331 — 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/LinFx/Extensions/Caching/DistributedCache.cs:1259` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/LinFx/Extensions/EventBus/Distributed/NullDistributedEventBus.cs:23 — src/LinFx/Extensions/EventBus/Distributed/NullDistributedEventBus.cs:23-35 | src/LinFx/Extensions/EventBus/Local/NullLocalEventBus.cs:21-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/LinFx.Extensions.AuditLogging/Domain/IAuditLogRepository.cs:16 — src/LinFx.Extensions.AuditLogging/Domain/IAuditLogRepository.cs:16-28 | src/LinFx.Extensions.AuditLogging/Domain/IAuditLogRepository.cs:33-45 — 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.

S1 · Web-Security Posture · Weak hash algorithm · ×3

Weak hash algorithm REDACTED:69 — MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
Weak hash algorithm REDACTED:83 — MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
Weak hash algorithm src/LinFx/Utils/StringExtensions.cs:379 — MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.

X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×3

Sync-over-async (deadlock risk) through `.Result` src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:456 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/LinFx.Extensions.EntityFrameworkCore/DependencyInjection/DbContextOptionsFactory.cs:120 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/LinFx.Extensions.EntityFrameworkCore/DependencyInjection/DbContextOptionsFactory.cs:124 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2

Duplicated block (14 lines × 2) src/LinFx/Extensions/ObjectExtending/Modularity/ExtensionPropertyConfiguration.cs:15 — src/LinFx/Extensions/ObjectExtending/Modularity/ExtensionPropertyConfiguration.cs:15-28 | src/LinFx/Extensions/ObjectExtending/ObjectExtensionPropertyInfo.cs:16-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) src/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs:78 — src/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs:78-91 | src/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs:172-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2

Duplicated block (10 lines × 2) src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:146 — src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:146-156 | src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:184-193 — 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/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:146` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:142 — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:142-151 | src/LinFx/Domain/Repositories/RepositoryBase.cs:83-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2

Duplicated block (6 lines × 2) src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:133 — src/LinFx/Domain/Repositories/BasicRepositoryBase.cs:133-138 | src/LinFx/Domain/Repositories/RepositoryBase.cs:74-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:203 — src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:203-208 | src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:330-335 — before extracting anything, compare `src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs` and `src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.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.

IC1 · Incompleteness & stubs · Skeleton type · ×2

Skeleton type — most members are unfinished src/LinFx.Extensions.AspNetCore/Mvc/MvcOptionsExtensions.cs:9 — `MvcOptionsExtensions` has 4 unfinished members out of 6 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented.
Skeleton type — most members are unfinished src/LinFx/Extensions/Logging/LoggerExtensions.cs:5 — `LoggerExtensions` has 2 unfinished members out of 4 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented.

IC1 · Incompleteness & stubs · Unfinished stub · ×2

Unfinished stub — throws NotImplementedException src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:150 — `DeleteAsync` 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/LinFx/Extensions/ObjectExtending/ExtensibleObject.cs:27 — `Validate` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.

IC1 · Incompleteness & stubs · Fake-async · ×2

Fake-async — async method never awaits src/LinFx/Extensions/Caching/DistributedCache.cs:1353 — `HandleExceptionAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/LinFx/Extensions/EventBus/Local/LocalEventErrorHandler.cs:33 — `ShouldRetryAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×2

Sync-over-async blocking — 1 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/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:118 — `.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).

S1 · Web-Security Posture · Password key derivation is priced too cheaply · ×2

Password key derivation is priced too cheaply src/LinFx/Security/Encryption/StringEncryptionService.cs:25 — This code fixes PBKDF2-SHA-1 at 1,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
Password key derivation is priced too cheaply src/LinFx/Security/Encryption/StringEncryptionService.cs:47 — This code fixes PBKDF2-SHA-1 at 1,000 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.

S1 · Web-Security Posture · Weak cipher · ×2

Weak cipher REDACTED:235 — DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes.
Weak cipher REDACTED:258 — DES / 3DES / RijndaelManaged-bare is deprecated or broken. Use AES-GCM via `Aes.Create()` with explicit key/iv sizes.

X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×2

Disposes a dependency it does not own src/LinFx.Extensions.MongoDB/Uow/MongoDB/MongoDbTransactionApi.cs:27 — `SessionHandle` is never created by `MongoDbTransactionApi` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 27). Its declared type `IClientSessionHandle` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/LinFx.Extensions.RabbitMQ/ChannelPool.cs:143 — `Channel` is never created by `ChannelPoolItem` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 143). Its declared type `IModel` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.

D1 · Cyclomatic Complexity · TypeHelper.GetSimplifiedName (cyclomatic 25) · ×1

TypeHelper.GetSimplifiedName (cyclomatic 25) src/LinFx/Reflection/TypeHelper.cs:188 — TypeHelper.GetSimplifiedName has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · RSAKeyExtensions.FromLvccXmlString (cyclomatic 19) · ×1

RSAKeyExtensions.FromLvccXmlString (cyclomatic 19) REDACTED:369 — RSAKeyExtensions.FromLvccXmlString has cyclomatic complexity 19 (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.

D1 · Cyclomatic Complexity · StringExtensions.ToSnakeCase (cyclomatic 17) · ×1

StringExtensions.ToSnakeCase (cyclomatic 17) src/LinFx/Utils/StringExtensions.cs:288 — StringExtensions.ToSnakeCase has cyclomatic complexity 17 (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.

D1 · Cyclomatic Complexity · EntityHistoryHelper.IsBaseAuditProperty (cyclomatic 17) · ×1

EntityHistoryHelper.IsBaseAuditProperty (cyclomatic 17) src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:269 — EntityHistoryHelper.IsBaseAuditProperty has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · EntityHistoryHelper.ShouldSavePropertyHistory (cyclomatic 16) · ×1

EntityHistoryHelper.ShouldSavePropertyHistory (cyclomatic 16) src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:213 — EntityHistoryHelper.ShouldSavePropertyHistory has cyclomatic complexity 16 (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.

D12 · Dependency Hygiene · Deprecated · ×1

Deprecated: System.IdentityModel.Tokens.Jwt REDACTED:30 — System.IdentityModel.Tokens.Jwt 7.5.1 — Legacy

D17 · Explicit Debt · BarePragmaDisable · ×1

BarePragmaDisable src/LinFx.Extensions.EntityFrameworkCore/ObjectExtending/EfObjectExtensionManagerExtensions.cs:139 — #pragma warning disable 618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.

D18 · Solution Shape · Build failed · ×1

Build failed — The target solution did not build cleanly (errors: 44), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0246: The type or namespace name 'JetBrains' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'NotNullAttribute' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'NotNull' could not be found (are you missing a using directive or an assembly reference?); CS1503: Argument 6: cannot convert from 'LinFx.Extensions.Timing.IClock' to 'Microsoft.Extensions.Internal.ISystemClock'; CS0246: The type or namespace name 'CanBeNullAttribute' could not be found (are you missing a using directive or an assembly reference?).

D2 · Cognitive Complexity · RSAKeyExtensions.FromLvccXmlString (cognitive 39) · ×1

RSAKeyExtensions.FromLvccXmlString (cognitive 39) REDACTED:369 — RSAKeyExtensions.FromLvccXmlString has cognitive complexity 39 (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.

D2 · Cognitive Complexity · ExtensibleObjectMapper.CanMapProperty (cognitive 32) · ×1

ExtensibleObjectMapper.CanMapProperty (cognitive 32) src/LinFx/Extensions/ObjectExtending/ExtensibleObjectMapper.cs:161 — ExtensibleObjectMapper.CanMapProperty has cognitive complexity 32 (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.

D2 · Cognitive Complexity · DistributedCache.GetOrAddMany (cognitive 26) · ×1

DistributedCache.GetOrAddMany (cognitive 26) src/LinFx/Extensions/Caching/DistributedCache.cs:484 — DistributedCache.GetOrAddMany has cognitive complexity 26 (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 (DistributedCache.GetOrAddManyAsync) 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.

D2 · Cognitive Complexity · DistributedCache.GetOrAddManyAsync (cognitive 26) · ×1

DistributedCache.GetOrAddManyAsync (cognitive 26) src/LinFx/Extensions/Caching/DistributedCache.cs:581 — DistributedCache.GetOrAddManyAsync has cognitive complexity 26 (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 (DistributedCache.GetOrAddMany) 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.

D2 · Cognitive Complexity · MongoModelBuilder.Build (cognitive 25) · ×1

MongoModelBuilder.Build (cognitive 25) src/LinFx.Extensions.MongoDB/MongoModelBuilder.cs:27 — MongoModelBuilder.Build has cognitive complexity 25 (threshold 15). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 53, 47, 92, …). 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.

D2 · Cognitive Complexity · EntityHistoryHelper.UpdateChangeList (cognitive 25) · ×1

EntityHistoryHelper.UpdateChangeList (cognitive 25) src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:325 — EntityHistoryHelper.UpdateChangeList has cognitive complexity 25 (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.

D2 · Cognitive Complexity · TypeHelper.GetSimplifiedName (cognitive 24) · ×1

TypeHelper.GetSimplifiedName (cognitive 24) src/LinFx/Reflection/TypeHelper.cs:188 — TypeHelper.GetSimplifiedName has cognitive complexity 24 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · CsvConverter.ExportCsv (cognitive 22) · ×1

CsvConverter.ExportCsv (cognitive 22) src/LinFx/Utils/CsvConverter.cs:36 — CsvConverter.ExportCsv has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RepositoryServiceCollectionExtensions.AddDefaultRepository (cognitive 21) · ×1

RepositoryServiceCollectionExtensions.AddDefaultRepository (cognitive 21) src/LinFx/Domain/DependencyInjection/RepositoryServiceCollectionExtensions.cs:9 — RepositoryServiceCollectionExtensions.AddDefaultRepository has cognitive complexity 21 (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.

D2 · Cognitive Complexity · FormattedStringValueExtracter.Extract (cognitive 21) · ×1

FormattedStringValueExtracter.Extract (cognitive 21) src/LinFx/Utils/FormattedStringValueExtracter.cs:21 — FormattedStringValueExtracter.Extract has cognitive complexity 21 (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.

D2 · Cognitive Complexity · SettingManager.GetAllAsync (cognitive 21) · ×1

SettingManager.GetAllAsync (cognitive 21) src/LinFx.Extensions.SettingManagement/Domain/SettingManager.cs:49 — SettingManager.GetAllAsync has cognitive complexity 21 (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.

D2 · Cognitive Complexity · FormatStringTokenizer.Tokenize (cognitive 20) · ×1

FormatStringTokenizer.Tokenize (cognitive 20) src/LinFx/Utils/FormatStringTokenizer.cs:7 — FormatStringTokenizer.Tokenize has cognitive complexity 20 (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.

D2 · Cognitive Complexity · DistributedCache.RemoveMany (cognitive 19) · ×1

DistributedCache.RemoveMany (cognitive 19) src/LinFx/Extensions/Caching/DistributedCache.cs:1231 — DistributedCache.RemoveMany has cognitive complexity 19 (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 (DistributedCache.RemoveManyAsync) 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.

D2 · Cognitive Complexity · DistributedCache.RemoveManyAsync (cognitive 19) · ×1

DistributedCache.RemoveManyAsync (cognitive 19) src/LinFx/Extensions/Caching/DistributedCache.cs:1292 — DistributedCache.RemoveManyAsync has cognitive complexity 19 (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 (DistributedCache.RemoveMany) 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.

D2 · Cognitive Complexity · EntityHistoryHelper.ShouldSavePropertyHistory (cognitive 19) · ×1

EntityHistoryHelper.ShouldSavePropertyHistory (cognitive 19) src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:213 — EntityHistoryHelper.ShouldSavePropertyHistory has cognitive complexity 19 (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.

D2 · Cognitive Complexity · EntityHelper.EntityEquals (cognitive 18) · ×1

EntityHelper.EntityEquals (cognitive 18) src/LinFx/Domain/Entities/EntityHelper.cs:18 — EntityHelper.EntityEquals has cognitive complexity 18 (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.

D2 · Cognitive Complexity · MongoDbRepository.DeleteManyAsync (cognitive 18) · ×1

MongoDbRepository.DeleteManyAsync (cognitive 18) src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:320 — MongoDbRepository.DeleteManyAsync has cognitive complexity 18 (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.

D2 · Cognitive Complexity · StringExtensions.ToSnakeCase (cognitive 17) · ×1

StringExtensions.ToSnakeCase (cognitive 17) src/LinFx/Utils/StringExtensions.cs:288 — StringExtensions.ToSnakeCase has cognitive complexity 17 (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.

D2 · Cognitive Complexity · EntityHistoryHelper.IsBaseAuditProperty (cognitive 16) · ×1

EntityHistoryHelper.IsBaseAuditProperty (cognitive 16) src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:269 — EntityHistoryHelper.IsBaseAuditProperty has cognitive complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · UnitOfWorkDbContextProvider.CreateDbContextWithTransactionAsync (cognitive 16) · ×1

UnitOfWorkDbContextProvider.CreateDbContextWithTransactionAsync (cognitive 16) src/LinFx.Extensions.EntityFrameworkCore/Uow/UnitOfWorkDbContextProvider.cs:102 — UnitOfWorkDbContextProvider.CreateDbContextWithTransactionAsync has cognitive complexity 16 (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.

D22 · Internal API Consistency · Inconsistent naming for retrieval operations. Permission and Feature controllers use 'GetAsync' for fetching by identifier/context, while Tenant controller uses 'GetAsync' for single entity and 'GetListAsync' for collections. More critically, the return types and parameter structures differ significantly between Permission/Feature (provider-based) and Tenant (ID-based), but the method names 'GetAsync' are overloaded with different semantic meanings (lookup by composite key vs lookup by ID). Additionally, Tenant has 'GetListAsync' while others lack a list endpoint, creating an asymmetry in CRUD surface area. · ×1

Inconsistent naming for retrieval operations. Permission and Feature controllers use 'GetAsync' for fetching by identifier/context, while Tenant controller uses 'GetAsync' for single entity and 'GetListAsync' for collections. More critically, the return types and parameter structures differ significantly between Permission/Feature (provider-based) and Tenant (ID-based), but the method names 'GetAsync' are overloaded with different semantic meanings (lookup by composite key vs lookup by ID). Additionally, Tenant has 'GetListAsync' while others lack a list endpoint, creating an asymmetry in CRUD surface area. — Standardize retrieval method names across all controllers. Use 'GetAsync' for single entity retrieval and 'GetListAsync' or 'QueryAsync' for collection retrieval. Ensure that controllers for similar domains (like Permission and Feature) have consistent parameter structures (e.g., both should support ID-based or provider-based lookups uniformly). Consider adding 'GetListAsync' to Permission and Feature controllers if they support listing, or remove 'GetListAsync' from Tenant if listing is not a core operation, to maintain parity. (signatures: PermissionController.GetAsync(string providerName, string providerKey) | FeatureController.GetAsync(string providerName, string providerKey) | TenantController.GetAsync(string id) | TenantController.GetListAsync(TenantRequest input))

D22 · Internal API Consistency · Inconsistent parameter structure for update operations. Permission and Feature controllers use a composite key (providerName, providerKey) for identification, while Tenant uses a simple ID string. This forces clients to handle different patterns for similar operations. Furthermore, the return types differ · ×1

Inconsistent parameter structure for update operations. Permission and Feature controllers use a composite key (providerName, providerKey) for identification, while Tenant uses a simple ID string. This forces clients to handle different patterns for similar operations. Furthermore, the return types differ: Permission and Feature UpdateAsync return Task (void), while Tenant UpdateAsync returns ValueTask<TenantDto> (the updated entity). This inconsistency in return values makes it difficult to write generic client code or error handling. — Standardize the return type for all UpdateAsync methods to return the updated entity (ValueTask<TDto>) to allow clients to verify the update. Standardize the identification mechanism: either all controllers should use a simple ID string, or all should use a provider/key pair if that is the domain model. If the domain models differ, ensure the API surface clearly documents this, but ideally, unify the pattern for similar operations. (signatures: PermissionController.UpdateAsync(string providerName, string providerKey, UpdatePermissionsDto input) | FeatureController.UpdateAsync(string providerName, string providerKey, UpdateFeaturesDto input) | TenantController.UpdateAsync(string id, TenantEditInput input))

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D3 · God Classes · FileTooLong · ×1

FileTooLong: Caching/DistributedCache.cs src/LinFx/Extensions/Caching/DistributedCache.cs — FileTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 184 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

D30 · Dependency Vulnerabilities · Medium CVE · ×1

REDACTED

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (4 members, 50+ identical tokens) src/LinFx/Extensions/Caching/DistributedCache.cs:165 — src/LinFx/Extensions/Caching/DistributedCache.cs:165-214 | src/LinFx/Extensions/Caching/DistributedCache.cs:241-299 | src/LinFx/Extensions/Caching/DistributedCache.cs:490-578 | src/LinFx/Extensions/Caching/DistributedCache.cs:588-674 — 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.

D4 · Code Duplication · Duplicated block (384 lines × 2) · ×1

Duplicated block (384 lines × 2) src/LinFx/Linq/IAsyncQueryableExecuter.cs:10 — src/LinFx/Linq/IAsyncQueryableExecuter.cs:10-393 | src/LinFx/Linq/IAsyncQueryableProvider.cs:12-395 — before extracting anything, compare `src/LinFx/Linq/IAsyncQueryableExecuter.cs` and `src/LinFx/Linq/IAsyncQueryableProvider.cs` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (39 lines × 2) · ×1

Duplicated block (39 lines × 2) samples/IdentityService.Host/Extensions/ExceptionToErrorInfoConverter.cs:26 — samples/IdentityService.Host/Extensions/ExceptionToErrorInfoConverter.cs:26-64 | src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.cs:61-99 — 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.

D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1

Duplicated block (26 lines × 2) src/LinFx/Extensions/Caching/DistributedCache.cs:540 — src/LinFx/Extensions/Caching/DistributedCache.cs:540-565 | src/LinFx/Extensions/Caching/DistributedCache.cs:636-661 — 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/LinFx/Extensions/Caching/DistributedCache.cs:540` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (20 lines × 4) · ×1

Duplicated block (20 lines × 4) src/LinFx/Extensions/Caching/DistributedCache.cs:173 — src/LinFx/Extensions/Caching/DistributedCache.cs:173-192 | src/LinFx/Extensions/Caching/DistributedCache.cs:254-273 | src/LinFx/Extensions/Caching/DistributedCache.cs:506-525 | src/LinFx/Extensions/Caching/DistributedCache.cs:602-621 — 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.

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1

Duplicated block (21 lines × 2) samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs:22 — samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs:22-42 | src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultHttpExceptionStatusCodeFinder.cs:23-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.

D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1

Duplicated block (16 lines × 3) src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:95 — src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:95-110 | src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:132-147 | src/LinFx/Extensions/EventBus/Local/LocalEventBus.cs:56-71 — before extracting anything, compare `src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs` and `src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.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.

D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1

Duplicated block (14–15 lines × 2) src/LinFx.Extensions.SettingManagement/Domain/SettingManagementStore.cs:93 — src/LinFx.Extensions.SettingManagement/Domain/SettingManagementStore.cs:93-107 | src/LinFx.Extensions.SettingManagement/Domain/SettingManagementStore.cs:178-191 — 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/LinFx.Extensions.SettingManagement/Domain/SettingManagementStore.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.

D4 · Code Duplication · Duplicated block (10–12 lines × 3) · ×1

Duplicated block (10–12 lines × 3) src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:211 — src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:211-220 | src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:338-349 | src/LinFx/Extensions/EventBus/Local/LocalEventBus.cs:101-110 — before extracting anything, compare `src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs` and `src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/LinFx/Extensions/EventBus/Local/LocalEventBus.cs:112` calls `GetOrCreateHandlerFactories`, `GetOrAdd` and `src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:222` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1

Duplicated block (11 lines × 3) src/LinFx/Domain/Entities/Events/Distributed/EntityCreatedEto.cs:16 — src/LinFx/Domain/Entities/Events/Distributed/EntityCreatedEto.cs:16-26 | src/LinFx/Domain/Entities/Events/Distributed/EntityDeletedEto.cs:16-26 | src/LinFx/Domain/Entities/Events/Distributed/EntityUpdatedEto.cs:16-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1

Duplicated block (16 lines × 2) src/LinFx/Extensions/Authorization/Permissions/PermissionDefinitionProvider.cs:19 — src/LinFx/Extensions/Authorization/Permissions/PermissionDefinitionProvider.cs:19-37 | src/LinFx/Extensions/Features/FeatureDefinitionProvider.cs:17-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/LinFx/Extensions/Authorization/Permissions/PermissionDefinitionProvider.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: LinFx.Extensions.EntityFrameworkCore src/LinFx.Extensions.EntityFrameworkCore/LinFx.Extensions.EntityFrameworkCore.csproj:1 — LinFx.Extensions.EntityFrameworkCore: abstractness 0.14, instability 0.14, distance 0.71 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.

D6 · Cohesion (LCOM4) · Low cohesion · ×1

Low cohesion: CommonDbContextRegistrationOptions (LCOM4 4) src/LinFx/Domain/DependencyInjection/CommonDbContextRegistrationOptions.cs:10 — CommonDbContextRegistrationOptions's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

P1 · CI/CD gates · No CI pipeline · ×1

No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1

Outbound HTTP without resilience — The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.

S1 · Web-Security Posture · Ciphertext is encrypted but not authenticated · ×1

Ciphertext is encrypted but not authenticated src/LinFx/Security/Encryption/StringEncryptionService.cs:29 — 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.

S1 · Web-Security Posture · The encryption IV is the same for every message · ×1

The encryption IV is the same for every message REDACTED:16 — This encryption's initialisation vector is a compile-time constant, so every message encrypted under the same key gets the same IV. An IV is not a secret and does not have to be one — its whole job is to be DIFFERENT each time, so that encrypting the same plaintext twice does not produce the same ciphertext. Fix it and CBC becomes an equality oracle: the mode XORs the IV into the first plaintext block and chains from there, so two messages encrypted with the same key and IV produce byte-identical ciphertext for exactly as long as their plaintexts agree. An observer who can see two ciphertexts — a repository of encrypted config files, a database column, a backup — learns that two records match and how many blocks in they diverge, without the key and without breaking anything. The same defect under a counter-based mode is worse and not recoverable by comparison: CTR and GCM XOR the plaintext against a keystream determined by the key and nonce, so a repeated nonce leaks the XOR of the two plaintexts outright, and under GCM it also forfeits the authentication key. Generate the IV with a cryptographic RNG for each message — `RandomNumberGenerator.Fill(iv)` in .NET, `crypto.randomBytes(16)` in Node — and write it alongside the ciphertext (prepending the block is the usual spelling); the receiver reads it back from there. Deriving the IV from the key material is the specific trap to avoid: it looks like rigour and produces a constant, because the derivation's inputs do not change between messages.

S1 · Web-Security Posture · Token validation disabled · ×1

Token validation disabled samples/IdentityService.Host/Application.cs:59 — `ValidateAudience`, `ValidateIssuer` are all set to `false`, which means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent.

SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1

NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.

X1 · Async correctness · Sync-over-async (deadlock risk) · ×1

Sync-over-async (deadlock risk) src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:118 — 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.

Minor — 226 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×126

Orphaned file src/LinFx/Linq/AsyncQueryableExecuter.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Extensions/Caching/IDistributedCache.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Security/Claims/JwtClaimTypes.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Domain/Repositories/RepositoryAsyncExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.MongoDB/MongoDbAsyncQueryableProvider.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.EntityFrameworkCore/EntityHistory/EntityHistoryHelper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.EventBus.RabbitMQ/RabbitMqDistributedEventBus.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.PermissionManagement/Application/PermissionService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Linq/IAsyncQueryableProvider.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Linq/IAsyncQueryableExecuter.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Extensions/EventBus/EventBusBase.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.EntityFrameworkCore/Modeling/EntityTypeBuilderExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Extensions/Uow/UnitOfWork.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Extensions/ObjectExtending/ExtensibleObjectValidator.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.Autofac/Autofac/Extensions/DependencyInjection/AutofacRegistration.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Extensions/ObjectExtending/ExtensibleObjectMapper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.EventBus.Kafka/KafkaDistributedEventBus.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Reflection/TypeHelper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.SettingManagement/Domain/SettingManagementStore.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx/Reflection/ReflectionHelper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/LinFx.Extensions.FeatureManagement/Domain/FeatureManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 101 more in this group — see findings.md.

X4 · Structured logging · Interpolated log message defeats structured logging · ×29

Interpolated log message defeats structured logging src/LinFx/Extensions/Logging/LoggerExtensions.cs:10 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx/Extensions/Modularity/ModuleHelper.cs:41 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.Kafka/ConsumerPool.cs:64 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.Kafka/ConsumerPool.cs:91 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.Kafka/ConsumerPool.cs:96 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.Kafka/ProducerPool.cs:69 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.Kafka/ProducerPool.cs:94 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.Kafka/ProducerPool.cs:99 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.EntityFrameworkCore/EfDbContext.cs:190 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.RabbitMQ/ChannelPool.cs:60 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.RabbitMQ/ChannelPool.cs:85 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.RabbitMQ/ChannelPool.cs:88 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:103 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:140 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:163 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.RabbitMQ/RabbitMqMessageConsumer.cs:179 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.AuditLogging/Domain/AuditingStore.cs:41 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:75 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:80 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:84 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:102 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:107 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:113 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:144 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:148 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
+ 4 more in this group — see findings.md.

IC1 · Incompleteness & stubs · Commented-out code · ×22

Commented-out code src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:89 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:90 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:93 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:105 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:106 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:107 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:115 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:137 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs:149 — 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/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatOptions.cs:24 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatOptions.cs:37 — 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/LinFx.Extensions.AspNetCore/Auditing/AspNetCoreAuditLogContributor.cs:29 — 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/LinFx.Extensions.AspNetCore/Auditing/AspNetCoreAuditLogContributor.cs:32 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/LinFx.Extensions.AspNetCore/Auditing/AspNetCoreAuditLogContributor.cs:37 — 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/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.cs:113 — 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/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.cs:116 — 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/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.cs:199 — 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/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.cs:202 — 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/LinFx.Extensions.AspNetCore/MultiTenancy/AspNetCoreMultiTenancyModule.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/LinFx.Extensions.AspNetCore/MultiTenancy/AspNetCoreMultiTenancyModule.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/LinFx.Extensions.AspNetCore/MultiTenancy/AspNetCoreMultiTenancyModule.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/LinFx.Extensions.AspNetCore/Mvc/AspNetCoreMvcModule.cs:32 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).

X10 · Duplicated predicate · Duplicated predicate · ×13

Duplicated predicate src/LinFx.Extensions.MongoDB/MongoDbContextHelper.cs:15 — `ReflectionHelper.IsAssignableToGenericType(property.PropertyType, typeof(IMongoCollection<>)) && typeof(IEntity).IsAssignableFrom(property.P…` appears character-identically in 2 files — src/LinFx.Extensions.MongoDB/MongoDbContextHelper.cs, src/LinFx.Extensions.MongoDB/MongoModelSource.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/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:621 — `distributedEvents != null && distributedEvents.Any()` appears character-identically in 2 files — src/LinFx.Extensions.EntityFrameworkCore/EfDbContext.cs, src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.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 samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs:25 — `exception is IHasErrorCode exceptionWithErrorCode && !exceptionWithErrorCode.Code.IsNullOrWhiteSpace()` appears character-identically in 2 files — samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs, src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultHttpExceptionStatusCodeFinder.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 samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs:22 — `exception is IHasHttpStatusCode exceptionWithHttpStatusCode && exceptionWithHttpStatusCode.HttpStatusCode > 0` appears character-identically in 2 files — samples/IdentityService.Host/Extensions/HttpExceptionStatusCodeFinder.cs, src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultHttpExceptionStatusCodeFinder.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 samples/IdentityService.Host/Extensions/ExceptionToErrorInfoConverter.cs:32 — `exception is RemoteCallException remoteCallException && remoteCallException.Error != null` appears character-identically in 2 files — samples/IdentityService.Host/Extensions/ExceptionToErrorInfoConverter.cs, src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.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 samples/IdentityService.Host/Extensions/ExceptionToErrorInfoConverter.cs:45 — `exception is UserFriendlyException || exception is RemoteCallException` appears character-identically in 2 files — samples/IdentityService.Host/Extensions/ExceptionToErrorInfoConverter.cs, src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.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/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:604 — `localEvents != null && localEvents.Any()` appears character-identically in 2 files — src/LinFx.Extensions.EntityFrameworkCore/EfDbContext.cs, src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.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/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:183 — `names.Contains(s.Name) && s.ProviderName == providerName && s.ProviderKey == providerKey` appears character-identically in 2 files — src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs, src/LinFx.Extensions.SettingManagement/EntityFrameworkCore/EfCoreSettingRepository.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/LinFx/Extensions/EventBus/Distributed/DistributedEventBusBase.cs:63 — `onUnitOfWorkComplete && UnitOfWorkManager.Current != null` appears character-identically in 2 files — src/LinFx/Extensions/EventBus/Distributed/DistributedEventBusBase.cs, src/LinFx/Extensions/EventBus/EventBusBase.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/LinFx.Extensions.FeatureManagement/Domain/FeatureManagementStore.cs:27 — `p.Name == name && p.ProviderName == providerName && p.ProviderKey == providerKey` appears character-identically in 2 files — src/LinFx.Extensions.FeatureManagement/Domain/FeatureManagementStore.cs, src/LinFx.Extensions.PermissionManagement/Application/PermissionService.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/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:146 — `s.ProviderName == providerName && s.ProviderKey == providerKey` appears character-identically in 2 files — src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs, src/LinFx.Extensions.SettingManagement/EntityFrameworkCore/EfCoreSettingRepository.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/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:660 — `typeof(ISoftDelete).IsAssignableFrom(typeof(TEntity)) && DataFilter.IsEnabled<ISoftDelete>()` appears character-identically in 2 files — src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs, src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepositoryFilterer.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/LinFx/Extensions/Validation/ValidationException.cs:104 — `validationResult.MemberNames != null && validationResult.MemberNames.Any()` appears character-identically in 2 files — src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultExceptionToErrorInfoConverter.cs, src/LinFx/Extensions/Validation/ValidationException.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.

AX6 · Interface segregation · Fat interface · ×4

Fat interface: IDistributedCache<TCacheItem, TCacheKey> (20 members) src/LinFx/Extensions/Caching/IDistributedCache.cs:19 — `IDistributedCache<TCacheItem, TCacheKey>` declares 20 members: `Get`, `GetMany`, `GetManyAsync`, `GetAsync`, `GetOrAdd`, `GetOrAddAsync`, `GetOrAddMany`, `GetOrAddManyAsync`, `Set`, `SetAsync`, `SetMany`, `SetManyAsync`, `Refresh`, `RefreshAsync`, `RefreshMany`, `RefreshManyAsync`, `Remove`, `RemoveAsync`, `RemoveMany`, `RemoveManyAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IUnitOfWork (19 members) src/LinFx/Extensions/Uow/IUnitOfWork.cs:8 — `IUnitOfWork` declares 19 members: `Id`, `Items`, `Failed`, `Disposed`, `Options`, `Outer`, `IsReserved`, `IsDisposed`, `IsCompleted`, `ReservationName`, `SetOuter`, `Initialize`, `Reserve`, `SaveChangesAsync`, `CompleteAsync`, `RollbackAsync`, `OnCompleted`, `AddOrReplaceLocalEvent`, `AddOrReplaceDistributedEvent`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IAsyncQueryableExecuter (66 members) src/LinFx/Linq/IAsyncQueryableExecuter.cs:6 — `IAsyncQueryableExecuter` declares 66 members: `ContainsAsync`, `AnyAsync`, `AnyAsync`, `AllAsync`, `CountAsync`, `CountAsync`, `LongCountAsync`, `LongCountAsync`, `FirstAsync`, `FirstAsync`, `FirstOrDefaultAsync`, `FirstOrDefaultAsync`, `LastAsync`, `LastAsync`, `LastOrDefaultAsync`, `LastOrDefaultAsync`, `SingleAsync`, `SingleAsync`, `SingleOrDefaultAsync`, `SingleOrDefaultAsync`, `MinAsync`, `MinAsync`, `MaxAsync`, `MaxAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, and 26 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 66 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 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: IAsyncQueryableProvider (67 members) src/LinFx/Linq/IAsyncQueryableProvider.cs:6 — `IAsyncQueryableProvider` declares 67 members: `CanExecute`, `ContainsAsync`, `AnyAsync`, `AnyAsync`, `AllAsync`, `CountAsync`, `CountAsync`, `LongCountAsync`, `LongCountAsync`, `FirstAsync`, `FirstAsync`, `FirstOrDefaultAsync`, `FirstOrDefaultAsync`, `LastAsync`, `LastAsync`, `LastOrDefaultAsync`, `LastOrDefaultAsync`, `SingleAsync`, `SingleAsync`, `SingleOrDefaultAsync`, `SingleOrDefaultAsync`, `MinAsync`, `MinAsync`, `MaxAsync`, `MaxAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, `SumAsync`, and 27 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 67 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

D17 · Explicit Debt · ObsoleteWithoutCallers · ×4

ObsoleteWithoutCallers src/LinFx/Domain/Repositories/IReadOnlyRepository.cs:12 — [Obsolete] WithDetailsAsync
ObsoleteWithoutCallers src/LinFx/Domain/Repositories/IReadOnlyRepository.cs:15 — [Obsolete] WithDetailsAsync
ObsoleteWithoutCallers src/LinFx/Domain/Repositories/RepositoryBase.cs:18 — [Obsolete] WithDetailsAsync
ObsoleteWithoutCallers src/LinFx/Domain/Repositories/RepositoryBase.cs:21 — [Obsolete] WithDetailsAsync

D34 · Knowledge Freshness · Most significant orphaned file · ×3

Most significant orphaned file src/LinFx/Extensions/Caching/DistributedCache.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/LinFx.Extensions.MongoDB/Domain/Repositories/MongoDB/MongoDbRepository.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/LinFx.Extensions.EntityFrameworkCore/EfDbContext.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.

X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×3

Diagnostic log message is built whether or not it is wanted src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:102 — `LogDebug` at line 102 is called with an argument built by `string.Join(",", cacheKeys)` (line 102), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Diagnostic log message is built whether or not it is wanted src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:107 — `LogDebug` at line 107 is called with an argument built by `string.Join(",", cacheKeys)` (line 107), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Diagnostic log message is built whether or not it is wanted src/LinFx.Extensions.PermissionManagement/Domain/PermissionStore.cs:113 — `LogDebug` at line 113 is called with an argument built by `string.Join(",", notCacheKeys)` (line 113), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.

D27 · Navigability · Pass-through layer · ×2

Pass-through layer REDACTED:11 — TenantController: all 5 public methods forward their arguments unchanged to TenantService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call TenantService directly, or give the layer a job.
Pass-through layer REDACTED:13 — FeatureController: all 3 public methods forward their arguments unchanged to FeatureAppService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call FeatureAppService directly, or give the layer a job.

S1 · Web-Security Posture · No security response headers detected · ×2

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 samples/IdentityService.Host/Program.cs:26 — 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.

S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2

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 samples/IdentityService.Host/Program.cs:26 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.

D12 · Dependency Hygiene · Outdated · ×1

Outdated: Swashbuckle.AspNetCore REDACTED:17 — Swashbuckle.AspNetCore 6.5.0 → 10.3.1 available (referenced by IdentityService.Host).

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Split LinFx · ×1

Split LinFx — A catch-all name that is huge (21k LoC) and sprawls across 57 unrelated namespaces. Suggested:

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D34 · Knowledge Freshness · Dormant codebase · ×1

Dormant codebase — 129 of 129 significant files have no living knowledge — the codebase as a whole is dormant, not 129 separate risks. Counted over 129 of the 832 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.

D9 · Test Distribution · No tests found · ×1

No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

M2 · Architecture documentation · No architecture diagram/doc · ×1

No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 10/21 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 21, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

P6 · Release Hygiene · No changelog · ×1

No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

PF1 · Benchmark discipline · No performance benchmarks · ×1

No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1

Not all async methods take a CancellationToken — Only 107/254 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.

X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1

Nullable reference types not enabled everywhere — 19/21 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1

Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.2 `!` suppressions per 1k syntax nodes — 22 suppression(s) across the 137668 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.

X7 · Silent fallback defaults · Silent fallback default in catch · ×1

Silent fallback default in catch src/LinFx/Utils/CultureHelper.cs:51 — `IsValidCultureCode` swallows `CultureNotFoundException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.

Minor — 45 finding(s)

D12 · Dependency Hygiene · Outdated · ×24

Outdated: Microsoft.AspNetCore.Authorization — Microsoft.AspNetCore.Authorization 8.0.4 → 10.0.13 available (referenced by LinFx).
Outdated: Microsoft.Extensions.Caching.Memory — REDACTED → 10.0.13 available (referenced by LinFx).
Outdated: Microsoft.Extensions.Caching.StackExchangeRedis — Microsoft.Extensions.Caching.StackExchangeRedis 8.0.4 → 10.0.13 available (referenced by LinFx).
Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 8.0.0 → 10.0.13 available (referenced by LinFx).
Outdated: Microsoft.Extensions.Http.Polly — Microsoft.Extensions.Http.Polly 8.0.4 → 10.0.13 available (referenced by LinFx).
Outdated: Microsoft.Extensions.Localization — Microsoft.Extensions.Localization 8.0.4 → 10.0.13 available (referenced by LinFx).
Outdated: System.IdentityModel.Tokens.Jwt — System.IdentityModel.Tokens.Jwt 7.5.1 → 8.23.0 available (referenced by LinFx).
Outdated: System.Text.Json — REDACTED → 10.0.13 available (referenced by LinFx).
Outdated: Microsoft.AspNetCore.Authentication.JwtBearer — Microsoft.AspNetCore.Authentication.JwtBearer 8.0.4 → 10.0.13 available (referenced by IdentityService.Host).
Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore — Microsoft.AspNetCore.Identity.EntityFrameworkCore 8.0.4 → 10.0.13 available (referenced by IdentityService.Host).
Outdated: Microsoft.EntityFrameworkCore.Sqlite — Microsoft.EntityFrameworkCore.Sqlite 8.0.4 → 10.0.13 available (referenced by IdentityService.Host).
Outdated: Microsoft.EntityFrameworkCore.Tools — Microsoft.EntityFrameworkCore.Tools 8.0.4 → 10.0.13 available (referenced by IdentityService.Host).
Outdated: Serilog.Extensions.Logging — Serilog.Extensions.Logging 8.0.0 → 10.0.0 available (referenced by IdentityService.Host).
Outdated: Serilog.Sinks.Async — Serilog.Sinks.Async 1.5.0 → 2.1.0 available (referenced by IdentityService.Host).
Outdated: Serilog.Sinks.Console — Serilog.Sinks.Console 5.0.1 → 6.1.1 available (referenced by IdentityService.Host).
Outdated: Serilog.Sinks.File — Serilog.Sinks.File 5.0.0 → 7.0.0 available (referenced by IdentityService.Host).
Outdated: Autofac.Extensions.DependencyInjection — Autofac.Extensions.DependencyInjection 9.0.0 → 11.0.2 available (referenced by LinFx.Extensions.Autofac).
Outdated: Autofac.Extras.DynamicProxy — Autofac.Extras.DynamicProxy 7.1.0 → 8.1.0 available (referenced by LinFx.Extensions.Autofac).
Outdated: MongoDB.Driver — MongoDB.Driver 2.24.0 → 3.12.0 available (referenced by LinFx.Extensions.MongoDB).
Outdated: Confluent.Kafka — Confluent.Kafka 2.3.0 → 2.16.0 available (referenced by LinFx.Extensions.Kafka).
Outdated: Microsoft.EntityFrameworkCore — Microsoft.EntityFrameworkCore 8.0.4 → 10.0.13 available (referenced by LinFx.Extensions.EntityFrameworkCore).
Outdated: Microsoft.EntityFrameworkCore.Relational — Microsoft.EntityFrameworkCore.Relational 8.0.4 → 10.0.13 available (referenced by LinFx.Extensions.EntityFrameworkCore).
Outdated: RabbitMQ.Client — RabbitMQ.Client 6.8.1 → 7.2.2 available (referenced by LinFx.Extensions.RabbitMQ).
Outdated: Npgsql.EntityFrameworkCore.PostgreSQL — Npgsql.EntityFrameworkCore.PostgreSQL 8.0.2 → 10.0.3 available (referenced by LinFx.Extensions.EntityFrameworkCore.PostgreSql).

D19 · Documentation Quality · XML-doc coverage · ×21

XML-doc coverage: LinFx REDACTED — LinFx: 33 % XML-doc coverage (826/2497).
XML-doc coverage: IdentityService.Host REDACTED — IdentityService.Host: 32 % XML-doc coverage (17/53).
XML-doc coverage: LinFx.Extensions.Autofac src/LinFx.Extensions.Autofac/LinFx.Extensions.Autofac.csproj — LinFx.Extensions.Autofac: 32 % XML-doc coverage (6/19).
XML-doc coverage: LinFx.Extensions.MongoDB REDACTED — LinFx.Extensions.MongoDB: 0 % XML-doc coverage (1/205).
XML-doc coverage: LinFx.Extensions.Kafka src/LinFx.Extensions.Kafka/LinFx.Extensions.Kafka.csproj — LinFx.Extensions.Kafka: 10 % XML-doc coverage (4/41).
XML-doc coverage: LinFx.Extensions.EntityFrameworkCore src/LinFx.Extensions.EntityFrameworkCore/LinFx.Extensions.EntityFrameworkCore.csproj — LinFx.Extensions.EntityFrameworkCore: 18 % XML-doc coverage (38/210).
XML-doc coverage: LinFx.Extensions.AspNetCore src/LinFx.Extensions.AspNetCore/LinFx.Extensions.AspNetCore.csproj — LinFx.Extensions.AspNetCore: 23 % XML-doc coverage (20/88).
XML-doc coverage: LinFx.Extensions.RabbitMQ src/LinFx.Extensions.RabbitMQ/LinFx.Extensions.RabbitMQ.csproj — LinFx.Extensions.RabbitMQ: 10 % XML-doc coverage (8/79).
XML-doc coverage: LinFx.Extensions.EventBus.RabbitMQ src/LinFx.Extensions.EventBus.RabbitMQ/LinFx.Extensions.EventBus.RabbitMQ.csproj — LinFx.Extensions.EventBus.RabbitMQ: 25 % XML-doc coverage (5/20).
XML-doc coverage: LinFx.Extensions.EventBus.Kafka src/LinFx.Extensions.EventBus.Kafka/LinFx.Extensions.EventBus.Kafka.csproj — LinFx.Extensions.EventBus.Kafka: 24 % XML-doc coverage (4/17).
XML-doc coverage: LinFx.Extensions.FeatureManagement src/LinFx.Extensions.FeatureManagement/LinFx.Extensions.FeatureManagement.csproj — LinFx.Extensions.FeatureManagement: 8 % XML-doc coverage (8/104).
XML-doc coverage: LinFx.Extensions.AuditLogging src/LinFx.Extensions.AuditLogging/LinFx.Extensions.AuditLogging.csproj — LinFx.Extensions.AuditLogging: 40 % XML-doc coverage (39/98).
XML-doc coverage: LinFx.Extensions.PermissionManagement src/LinFx.Extensions.PermissionManagement/LinFx.Extensions.PermissionManagement.csproj — LinFx.Extensions.PermissionManagement: 32 % XML-doc coverage (27/84).
XML-doc coverage: LinFx.Extensions.TenantManagement src/LinFx.Extensions.TenantManagement/LinFx.Extensions.TenantManagement.csproj — LinFx.Extensions.TenantManagement: 40 % XML-doc coverage (14/35).
XML-doc coverage: LinFx.Extensions.PermissionManagement.HttpApi src/LinFx.Extensions.PermissionManagement.HttpApi/LinFx.Extensions.PermissionManagement.HttpApi.csproj — LinFx.Extensions.PermissionManagement.HttpApi: 100 % XML-doc coverage (3/3).
XML-doc coverage: LinFx.Extensions.TenantManagement.HttpApi src/LinFx.Extensions.TenantManagement.HttpApi/LinFx.Extensions.TenantManagement.HttpApi.csproj — LinFx.Extensions.TenantManagement.HttpApi: 100 % XML-doc coverage (6/6).
XML-doc coverage: LinFx.Extensions.FeatureManagement.HttpApi src/LinFx.Extensions.FeatureManagement.HttpApi/LinFx.Extensions.FeatureManagement.HttpApi.csproj — LinFx.Extensions.FeatureManagement.HttpApi: 100 % XML-doc coverage (4/4).
XML-doc coverage: LinFx.Extensions.EntityFrameworkCore.Sqlite src/LinFx.Extensions.EntityFrameworkCore.Sqlite/LinFx.Extensions.EntityFrameworkCore.Sqlite.csproj — LinFx.Extensions.EntityFrameworkCore.Sqlite: 0 % XML-doc coverage (0/8).
XML-doc coverage: LinFx.Extensions.EntityFrameworkCore.PostgreSql REDACTED — LinFx.Extensions.EntityFrameworkCore.PostgreSql: 0 % XML-doc coverage (0/9).
XML-doc coverage: LinFx.Extensions.AspNetCore.Authentication.WeChat src/LinFx.Extensions.AspNetCore.Authentication.WeChat/LinFx.Extensions.AspNetCore.Authentication.WeChat.csproj — LinFx.Extensions.AspNetCore.Authentication.WeChat: 37 % XML-doc coverage (11/30).
XML-doc coverage: LinFx.Extensions.SettingManagement src/LinFx.Extensions.SettingManagement/LinFx.Extensions.SettingManagement.csproj — LinFx.Extensions.SettingManagement: 4 % XML-doc coverage (4/111).

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dc27091aca9f41f98ada17ab42c882a9/history.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dc27091aca9f41f98ada17ab42c882a9/tree.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	11	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list LinFx.sln package --vulnerable --include-transitive --format json	9	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	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 106 file(s) — `src/LinFx.Extensions.AspNetCore.Authentication.WeChat/CachedPropertiesDataFormat.cs`, `src/LinFx.Extensions.AspNetCore.Authentication.WeChat/WeChatHandler.cs`, `src/LinFx.Extensions.AspNetCore/Auditing/AuditingMiddleware.cs`, `src/LinFx.Extensions.AspNetCore/ExceptionHandling/DefaultHttpExceptionStatusCodeFinder.cs`, `src/LinFx.Extensions.AspNetCore/ExceptionHandling/ExceptionHandlingMiddleware.cs`, … (+101 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	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.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	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.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	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.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	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.	0	—
D43 · Malicious Dependencies	none (no readable dependency manifest)	—	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 01a160f9-31ad-79b4-8793-6e5e2729d30f · 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 — 8 field(s) across 3 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.

Name — 4 field(s)

EntityChange.EntityTypeFullName src/LinFx.Extensions.AuditLogging/Domain/EntityChange.cs:26
EntityPropertyChange.PropertyTypeFullName src/LinFx.Extensions.AuditLogging/Domain/EntityPropertyChange.cs:23
EntityPropertyChangeInfo.PropertyTypeFullName src/LinFx/Domain/Entities/EntityPropertyChangeInfo.cs:30
EntityChangeInfo.EntityTypeFullName src/LinFx/Extensions/Auditing/EntityChangeInfo.cs:28

Email — 2 field(s)

CurrentUser.Email src/LinFx/Security/Users/CurrentUser.cs:26
ICurrentUser.Email src/LinFx/Security/Users/ICurrentUser.cs:35

Phone — 2 field(s)

CurrentUser.PhoneNumber src/LinFx/Security/Users/CurrentUser.cs:22
ICurrentUser.PhoneNumber src/LinFx/Security/Users/ICurrentUser.cs:28

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 53% · Adequate · gated by D18, X4 ·

At a glance — Architecture · 97% · Exemplary ·

At a glance — Maturity · 39% · Weak · gated by D34, M2 ·

At a glance — Readiness · 17% · Critical · gated by D8, D9, D12, D13, P1, P3, P7 ·

At a glance — Security · 46% · Weak · gated by C1, S1 ·

At a glance — Event-Driven · 100% · Exemplary ·

At a glance — Performance · 56% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts