Raiffeisen-DGTL/ViennaNET

Executive summary

Raiffeisen-DGTL/ViennaNET scores 42 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Maturity, which scores 34 and is rated Weak. Its Knowledge Freshness dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 1 No ADRs found finding(s) in ADR Quality and to resolve the 7 Vulnerable finding(s) in Dependency Hygiene, and if Maturity rose to 70, the score would rise from 42 to about 50.

55 findings are critical: 18 in Dependency Vulnerabilities, 14 in Static Analysis (SAST), ten in Explicit Debt, seven in Dependency Hygiene, three in Project dependency cycles, two in Secrets (history) and one in Async correctness.

Watchdog couldn't measure Runtime accessibility in this code, so that dimension is left out of the score. The product code is 36,496 lines, which would take an estimated 0.5 person-years, around €70,000, to rebuild.

Code Health 71 Strong Architecture 91 ★ Exemplary Maturity 34 Weak, capped by Knowledge Freshness, Architecture documentation and Documentation accuracy Production Readiness 42 Weak, capped by Dependency Hygiene and Outbound HTTP resilience Security and Compliance 44 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing, Data Protection and Access Controls Performance 60 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.

Maturity 34 · counts for 46%Production Readiness 42 · counts for 25%Security and Compliance 44 · counts for 14%Performance 60 · counts for 8%Code Health 71 · counts for 4%Architecture 91 · counts for 2%

If Maturity rose from 34 to 70, the lowest score rated Strong, the score would rise from 42 to about 50.

Code composition: what the lines of code are

Business logic 17%Supporting code 43%Tests 40%Generated by tools 0%

New since the last survey: 60 findings

These 60 critical or serious findings weren't in the previous survey, on 7 October 2026.

Coupling · Unstable project ViennaNET.WebApi.Configurators.Security.Jwt src/ViennaNET.WebApi.Configurators.Security.Jwt/ViennaNET.WebApi.Configurators.Security.Jwt.csproj
Explicit Debt · EmptyCatchBlock src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs
Explicit Debt · EmptyCatchBlock src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs
Explicit Debt · EmptyCatchBlock src/ViennaNET.Logging/ScopeLogRedirector.cs
Explicit Debt · EmptyCatchBlock src/ViennaNET.Word/Document.cs
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Supply-chain Provenance & Signing · REDACTED
Async correctness · Sync-over-async (deadlock risk) through `.Result` src/ViennaNET.Messaging/Sending/Impl/MessageSender.cs
Cancellation propagation · Async method without CancellationToken: ObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: ObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashObjectGetAllAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: ObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: ObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: ObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: StringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: StringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashStringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashStringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashStringGetAllAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: StringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: StringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: StringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashStringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: HashStringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs
Cancellation propagation · Async method without CancellationToken: SaveAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: ConfigGetAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: ConfigSetAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: InfoAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: LastSaveAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: TimeAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: FlushAllDatabasesAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: FlushDatabaseAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs
Cancellation propagation · Async method without CancellationToken: ValidateAsync src/ViennaNET.Validation/Rules/FluentRule/BaseFluentRuleAsync.cs
Cancellation propagation · Async method without CancellationToken: ValidateAsync src/ViennaNET.Validation/Rules/FluentRule/PropertyRuleValidationMember.cs
Cancellation propagation · Async method without CancellationToken: ValidateAsync src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/PropertyRuleValidatorAsync.cs
Cancellation propagation · Async method without CancellationToken: ValidateAsync src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/UseIRulePropertyValidatorAsync.cs
Cancellation propagation · Async method without CancellationToken: ProcessAsync src/ViennaNET.Validation/ValidationChains/CompositeValidationChainMember.cs
Cancellation propagation · Async method without CancellationToken: ProcessAsync src/ViennaNET.Validation/ValidationChains/StopOnFailureChainMemberDecorator.cs
Cancellation propagation · Async method without CancellationToken: ProcessAsync src/ViennaNET.Validation/ValidationChains/ValidationChainMember.cs
Cancellation propagation · Async method without CancellationToken: ValidateManyAsync src/ViennaNET.Validation/Validators/ValidatorAsync.cs
Exception handling · Swallowed exception (empty catch) src/ViennaNET.Logging/ScopeLogRedirector.cs
Exception handling · Swallowed exception (empty catch) src/ViennaNET.Word/Document.cs
Exception handling · Swallowed exception (empty catch) src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs
Exception handling · Swallowed exception (empty catch) src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs
Outbound HTTP resilience · Outbound HTTP without resilience src/ViennaNET.KasperskyScanEngine.Client/DependencyInjection/KseServiceCollectionExtensions.cs
Outbound HTTP resilience · Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.Basic/BasicHttpClientsConfigurator.cs
Outbound HTTP resilience · Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.Jwt/JwtHttpClientsConfigurator.cs
Outbound HTTP resilience · Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.NoAuthentication/NoAuthenticationHttpClientsConfigurator.cs
Outbound HTTP resilience · Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.Ntlm/NtlmHttpClientsConfigurator.cs
Async & latency hygiene · Sync-over-async blocking
Async & latency hygiene · Sync-over-async blocking src/ViennaNET.Messaging/Processing/Impl/Polling.cs
Async & latency hygiene · Sync-over-async blocking src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs
Async & latency hygiene · Sync-over-async blocking src/ViennaNET.Extensions.Configuration.HashicorpVault/VaultConfigurationProvider.cs

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 6 findings

These 6 critical or serious findings were in the previous survey, on 7 October 2026, and are gone from this one.

Coupling · Off the main sequence: ViennaNET.SimpleInjector.Extensions
Coupling · Off the main sequence: ViennaNET.Extensions.Http
Supply-chain Provenance & Signing REDACTED
Exception handling · Swallowed exception (caught, then discarded) src/ViennaNET.HttpClient/HttpResponseMessageExtensions.cs
Exception handling · Swallowed exception (caught, then discarded) src/ViennaNET.Excel/Impls/NPoiWorkSheet.cs
Exception handling · Swallowed exception (caught, then discarded) src/ViennaNET.WebApi.Configurators.SimpleInjector/SimpleInjectorConfigurator.cs

Rebuild cost: about €70,000 · Estimate

Cost to rebuild	€23,000 to €120,000, for 384 to 1,223 hours of work, about 0.5 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 42. 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: 36,496 lines of product code
Comment lines	The estimate prices 26,414 lines. Comment lines count towards the size of 36,496 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 1 No ADRs found finding(s) in ADR Quality.

Raises the score by about 6 points · Low effort · ADR Quality

Resolve the 7 Vulnerable finding(s) in Dependency Hygiene.

Raises the score by about 4 points · Low effort · Dependency Hygiene

Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with ViennaNET.WebApi.csproj (2), ViennaNET.Security.Jwt.csproj (2), REDACTED.

Raises the score by about 4 points · Low effort · Dependency Hygiene

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.

Where the investment is most exposed · Value at risk

This code would cost about €70,000 to build again, about 0.5 person-years of work. Its weakest lens is Maturity, at 34 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.

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

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

If you do one thing first · First action

Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — 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.

168 modules, with 222 dependencies between them. 3 loops run through 12 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 128 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 CallContext	2 Diagnostic.Data	4 Mediator.Seedwork	5 Messaging.Configuration	6 Messaging.Messages	7 Messaging.Processing	8 Orm.Configuration	9 Validation.Rules.ValidationResults.RuleMessages	10 WebApi.Abstractions	12 Diagnostic	13 Logging.Configuration	15 Messaging	16 Messaging.Context	17 Messaging.Tools	18 Orm	19 Validation.Rules.ValidationResults	20 Validation.ValidationChains	23 Logging.Contracts	24 Messaging.Factories	26 Orm.Factories	27 Validation.Validators	28 Logging	29 Messaging.Factories.Impl	30 Messaging.Processing.Impl	31 Orm.Repositories	32 Validation.Rules	38 Orm.Application
1 CallContext
2 Diagnostic.Data
3 HttpClient
4 Mediator.Seedwork
5 Messaging.Configuration
6 Messaging.Messages
7 Messaging.Processing
8 Orm.Configuration
9 Validation.Rules.ValidationResults.RuleMessages
10 WebApi.Abstractions
11 WebApi.Configurators.HttpClients.Abstractions.Configuration
12 Diagnostic		3
13 Logging.Configuration																		10				2
14 Mediator			2
15 Messaging				1	7
16 Messaging.Context	4				1
17 Messaging.Tools					3
18 Orm																											3
19 Validation.Rules.ValidationResults								1																		1
20 Validation.ValidationChains																					9					12
21 WebApi.Configurators.Security.Jwt	2								1
22 WebApi.Configurators.Security.Ntlm	1								1
23 Logging.Contracts											2											3
24 Messaging.Factories												2
25 Messaging.Sending.Impl	3				1							3		3
26 Orm.Factories							2								6												4
27 Validation.Validators								1								1	6									21
28 Logging																		5
29 Messaging.Factories.Impl	1			1								2		2					5
30 Messaging.Processing.Impl						3				1		2	1						1
31 Orm.Repositories															5					1							8
32 Validation.Rules																4					1
33 Messaging.ActiveMQQueue				3	4							4											1
34 Messaging.KafkaQueue				3	4							3		2									1
35 Messaging.MQSeriesQueue				3	4							4											1
36 Messaging.Processing.Impl.Poll					3	1				3		9	3											1
37 Messaging.Processing.Impl.Subscribe	1				3	1				3		7	4											1
38 Orm.Application																									2
39 Validation.Rules.FluentRule								3								2	2				1					11
40 EventSourcing			2																1								1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 71% · Strong ·

The Good

D1 · .NET / C# Cyclomatic Complexity 9.8 D2 · .NET / C# Cognitive Complexity 8.2 D3 · .NET / C# God Classes 9.1 D4 · .NET / C# Code Duplication 9.6 D17 · .NET / C# Explicit Debt 8.3 D18 · .NET / C# Solution Shape 9.2 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.2 X1 · Repo Async correctness 7.1 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 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 7.6 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.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.9

The Bad

X2 · Repo Cancellation propagation 6.2 X4 · Repo Structured logging 6.4

The Ugly

X18 · Repo Disposal-pattern correctness 5.0

At a glance — Architecture · 91% · Exemplary ·

The Good

D5 · .NET / C# Coupling 9.5 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 8.6 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 7.1 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 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0

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

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 7.9 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 7.7 M3 · Repo Folder & project structure 10.0

The Bad

M1 · Repo Documentation (README) 6.9

The Ugly

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

At a glance — Readiness · 42% · Weak · gated by D12, P7 ·

The Good

D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 9.9 D11 · .NET / C# Test Reliability 10.0 D13 · .NET / C# REDACTED Scanning 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.7 P6 · Repo Release Hygiene 10.0

The Bad

P4 · Repo Deployment & Rollback 5.0

The Ugly

D12 · .NET / C# Dependency Hygiene 0.0 P3 · Repo Security & performance tooling 4.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 44% · Weak · gated by D29, D30, D36, C1, C2 ·

The Good

D28 · .NET / C# Secrets (history) 8.0 D37 · .NET / C# Vulnerability-disclosure Policy 10.0 D44 · .NET / C# Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 8.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

C4 · Repo Data Retention 6.5

The Ugly

D29 · .NET / C# Static Analysis (SAST) 3.7 D30 · .NET / C# Dependency Vulnerabilities 0.0 D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 3.0 C2 · Repo Access Controls 3.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

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
A03:2025 — Software Supply Chain Failures	33	High / Critical
A05:2025 — Injection	23	High / Critical
A07:2025 — Authentication Failures	3	High / Critical

Roadmap

Begin by resolving the 169 orphaned files in the codebase, prioritizing Mediator.cs and related interfaces, and immediately address the seven vulnerable dependencies to secure the project. Next, establish architectural governance by creating an ADR folder and documenting significant design decisions with their dates and consequences. Finally, reconcile the README files with the actual repository structure to eliminate contradictions regarding the architecture and missing package references.

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

Do this	Helps	Effort	Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+6.3 pts	Low	ADR Quality
Resolve the 7 Vulnerable finding(s) in Dependency Hygiene.	+4.0 pts	Low	Dependency Hygiene
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with ViennaNET.WebApi.csproj (2), ViennaNET.Security.Jwt.csproj (2), REDACTED.	+3.8 pts	Low	Dependency Hygiene
Resolve the 5 Outdated finding(s) in Dependency Hygiene — start with Directory.Build.props (2), ViennaNET.Orm.Oracle.csproj, ViennaNET.WebApi.Configurators.Swagger.UiJwtAuth.csproj.	+3.5 pts	Low	Dependency Hygiene
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.	+5.9 pts	Medium	Architecture documentation
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; src/ViennaNET.Extensions.Configuration.HashicorpVault/README.md installs the package `ViennaNET.Extensions.Configuration.HashicorpVault` (`dotnet add package ViennaNET.Extensions.Configuration.HashicorpVault`), but no project or props file references it; src/ViennaNET.Extensions.Http/README.md installs the package `ViennaNET.Extensions.Http` (`dotnet add package ViennaNET.Extensions.Http`), but no project or props file references it; src/ViennaNET.KasperskyScanEngine.Client/README.md installs the package `ViennaNET.KasperskyScanEngine.Client` (`dotnet add package ViennaNET.KasperskyScanEngine.Client`), but no project or props file references it.	+4.9 pts	Medium	Documentation accuracy
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.	+2.4 pts	Low	Documentation Quality
Resolve the 169 Orphaned file finding(s) in Knowledge Freshness — start with Mediator.cs (2), IMediator.cs (2), CurrentValidatorHolderExtensions.cs.	+7.8 pts	High	Knowledge Freshness

File quality

Per-file score 0–10 — a quality signature. Of 128 files carrying findings, judged against the Production bar: 2% slop · 32% mixed · 66% near-clean.

File	Score	Band	Worst signal
REDACTED	0.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	1.2	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	1.6	Slop	Static Analysis (SAST): High: REDACTED
src/ViennaNET.Logging/Logger.cs	4.3	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	5.1	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	5.3	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
src/ViennaNET.Word/Document.cs	5.4	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	5.7	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	5.7	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	5.8	Mixed	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	5.8	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	5.8	Mixed	Dependency Vulnerabilities: Medium CVE: REDACTED
src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs	6.0	Mixed	Explicit Debt: CoverageExclusion
src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs	6.4	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	6.7	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
src/ViennaNET.Mediator/IMessageHandler.cs	6.9	Mixed	Explicit Debt: ObsoleteWithCallers
src/ViennaNET.Mediator/IMessageHandlerAsync.cs	6.9	Mixed	Explicit Debt: ObsoleteWithCallers
REDACTED	6.9	Mixed	Dependency Vulnerabilities: Medium CVE: REDACTED
src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs	7.1	Mixed	Code Duplication: Duplicated block (17 lines × 2)
src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs	7.2	Mixed	Cyclomatic Complexity: CustomRollingFileAppender.InitializeFromOneFile (cyclomatic 17)

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

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

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

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

Could not be resolved — 4

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

Methodology & how to trust this report

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

D1D2D3D4D5D6D9D10D11D12D13D14D15D17D18D19D20D21D24D26D27D28D29D30D34D35D36D37D39D44AX1AX10AX2AX3AX5AX6AX8AX9C1C2C4GD1IC1M1M2M3M4P1P2P3P4P6P7PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 579 of 659 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 01a16132-469b-7085-a16c-ba42609212fb.

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. All 172 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 170 of the 613 production source files in this repository: 441 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/ViennaNET.ArcSight/ViennaNET.ArcSight.csproj' with message: Package 'SyslogNet.Client 0.3.3' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NET….
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (36,438 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
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/ViennaNET.WebApi.Abstractions). 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 'ViennaNET.WebApi.Abstractions.csproj'`: Unable to proceed with project 'src/ViennaNET.WebApi.Abstractions/ViennaNET.WebApi.Abstractions.csproj'. Ensure you have a runnable project type. A…; runtime evidence skipped (launch chosen because src/ViennaNET.WebApi.Abstractions/ViennaNET.WebApi.Abstractions.csproj is a Microsoft.NET.Sdk.Web project).
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. 26 further occurrence(s) are not listed individually; the score already reflects all 66.

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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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 (4): D19, D21, D24, 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.8 / 10Stronggated by 1 serious finding✓ 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.8 / 10 · rule-coverage 100% · ceiling Prevented

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CustomRollingFileAppender.InitializeFromOneFile at 17.

CustomRollingFileAppender.InitializeFromOneFile (cyclomatic 17)src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs:993

What to do

Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with CustomRollingFileAppender.InitializeFromOneFile (cyclomatic 17). — Refactoring it lifts Cyclomatic Complexity from 9.8 to about 10.0/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity8.2 / 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 8.2 / 10 · rule-coverage 100% · ceiling Prevented

8 method(s) exceeded the cognitive complexity threshold of 15; the worst was CustomRollingFileAppender.RollOverRenameFiles at 43.

CustomRollingFileAppender.RollOverRenameFiles (cognitive 43)src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs:1538

CustomRollingFileAppender.InitializeFromOneFile (cognitive 27)src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs:993

Log4NetConfigurationApplier.GetFileAppender (cognitive 25)src/ViennaNET.Logging/Log4NetImpl/Log4NetConfigurationApplier.cs:137

ApplicationContextProvider.RegisterBoundedContexts (cognitive 17)src/ViennaNET.Orm/Factories/ApplicationContextProvider.cs:65

Validator.CheckDependsOnMembers (cognitive 16)src/ViennaNET.Validation/Validators/Validator.cs:129

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

What to do

Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with CustomRollingFileAppender.RollOverRenameFiles (cognitive 43). — Refactoring it lifts Cognitive Complexity from 8.3 to about 8.6/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.1 / 10Stronggated by 8 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.1 / 10 · rule-coverage 100% · ceiling Prevented

8 god class(es) detected.

TooManyMethods: RedisDatabase · ×4src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs

MethodTooLong: ExtensionsRule.ExtensionsRule(…) · ×3src/ViennaNET.ArcSight/Validation/ExtensionsRule.cs:7

ClassTooLong: CustomRollingFileAppendersrc/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs

What to do

Resolve the 4 TooManyMethods finding(s) in God Classes — start with RedisDatabase.cs, SilentRedisDatabase.cs, CompanyHostBuilderActions.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with CefMessageSerializer.cs (2), ExtensionsRule.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 ClassTooLong finding(s) in God Classes — start with CustomRollingFileAppender.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.6 / 10Stronggated by 27 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.6 / 10 · rule-coverage 100% · ceiling Verified

27 duplicated block group(s) detected.

Duplicated block (5 lines × 2) · ×4src/ViennaNET.Validation/Validators/IValidatorExtensions.cs:88

Duplicated block (8 lines × 2) · ×3src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/InclusiveBetweenValidator.cs:13

Duplicated block (13 lines × 2) · ×2src/ViennaNET.Messaging.ActiveMQQueue/ActiveMqQueueMessageConverter.cs:91

Duplicated block (9 lines × 2) · ×2src/ViennaNET.Word/Document.cs:130

Duplicated block (7 lines × 2) · ×2src/ViennaNET.Word/WordprocessingDocumentFactory.cs:17

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

What to do

Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with IValidatorExtensions.cs, BaseFluentRule.cs, KafkaQueueMessageAdapter.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with InclusiveBetweenValidator.cs, KafkaQueueMessageAdapter.cs, JwtGenerationConfigurator.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with ActiveMqQueueMessageConverter.cs, ActiveMQQueueMessageAdapter.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling9.5 / 10Stronggated by 7 serious findings✓ Tool-verified

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

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

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

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

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

Off the main sequence: ViennaNET.Orm.DB2.NHibernateDriver · ×4REDACTED:1

Unstable project ViennaNET.WebApi.Configurators.Security.Jwtsrc/ViennaNET.WebApi.Configurators.Security.Jwt/ViennaNET.WebApi.Configurators.Security.Jwt.csproj:1

Unstable project ViennaNET.WebApi.Configurators.HttpClients.Ntlmsrc/ViennaNET.WebApi.Configurators.HttpClients.Ntlm/ViennaNET.WebApi.Configurators.HttpClients.Ntlm.csproj:1

Unstable project ViennaNET.WebApi.Configurators.HttpClients.Jwtsrc/ViennaNET.WebApi.Configurators.HttpClients.Jwt/ViennaNET.WebApi.Configurators.HttpClients.Jwt.csproj:1

What to do

Resolve the 4 Off the main sequence finding(s) in Coupling — start with REDACTED, ViennaNET.Utils.csproj, ViennaNET.HttpClient.csproj. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Unstable project ViennaNET.WebApi.Configurators.Security.Jwt finding(s) in Coupling — start with ViennaNET.WebApi.Configurators.Security.Jwt.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project ViennaNET.WebApi.Configurators.HttpClients.Ntlm finding(s) in Coupling — start with ViennaNET.WebApi.Configurators.HttpClients.Ntlm.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 104 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

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

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

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

917 test methods: 917 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

2 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 922 tests.

Skipped test: CefSender_SendCef · ×2tests/ViennaNET.ArcSight.Tests/Integration/TestClient.cs:9

No assertions: ConcurrentSendMessageAsyncTest · ×2tests/ViennaNET.Mediator.Tests/Units/Mediators/MediatorTests.cs:278

Mock-dominated test: Send_CorrectSettingsAndMessage_MessageCorrectlySent · ×13tests/ViennaNET.ArcSight.Tests/Unit/ArcSightClientTests.cs:49

What to do

Resolve the 13 Mock-dominated test finding(s) in Test Quality — start with ScopedSessionManagerTests.cs (8), UnitOfWorkTests.cs (2), ArcSightClientTests.cs. — One of this dimension's main actionable groups (13 recommendation-level).
Resolve the 2 Skipped test finding(s) in Test Quality — start with TestClient.cs, WordDocumentFactoryTests.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 No assertions finding(s) in Test Quality — start with MediatorTests.cs, WhenClauseTests.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Verified

52 outdated, 7 vulnerable, 6 deprecated packages.

Vulnerable: log4net · ×7

Deprecated: App.Metrics.AspNetCore.Mvc · ×6src/ViennaNET.WebApi/ViennaNET.WebApi.csproj:8

Outdated: coverlet.msbuild · ×5tests/Directory.Build.props:26

Outdated: Newtonsoft.Json · ×47

What to do

Resolve the 7 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with ViennaNET.WebApi.csproj (2), ViennaNET.Security.Jwt.csproj (2), REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Outdated finding(s) in Dependency Hygiene — start with Directory.Build.props (2), ViennaNET.Orm.Oracle.csproj, ViennaNET.WebApi.Configurators.Swagger.UiJwtAuth.csproj. — One of this dimension's main actionable groups (5 recommendation-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 319 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 62 direct `PackageReference`(s), and 188 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 Debt8.3 / 10Adequategated by 10 critical findings✓ 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 8.3 / 10 · rule-coverage 100% · ceiling Prevented

57 deducted debt markers + unmeasured dead symbols across 36438 LoC in the .NET projects (0.9/KLoC) → score 8.3. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

WriteOnlyPrivateField · ×5src/ViennaNET.Excel/Impls/NPoiExcelFile.cs:36

EmptyCatchBlock · ×5src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs:83

ObsoleteWithCallers · ×22src/ViennaNET.Excel/IO/IFileUtils.cs:7

CoverageExclusion · ×16src/ViennaNET.Logging/DefaultCategoryLogger.cs:10

BareSuppressMessage · ×5src/ViennaNET.Extensions.Mediator/DependencyInjection/MediatorServiceCollectionExtensions.cs:39

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

What to do

Resolve the 5 WriteOnlyPrivateField finding(s) in Explicit Debt — start with NPoiExcelFile.cs, Polling.cs, CommandExecutor.cs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 5 EmptyCatchBlock finding(s) in Explicit Debt — start with NPoiExcelProvider.cs (2), Logger.cs, ScopeLogRedirector.cs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 22 ObsoleteWithCallers finding(s) in Explicit Debt — start with IMessageHandler.cs (3), IMessageHandlerAsync.cs (3), IFileUtils.cs. — One of this dimension's main actionable groups (22 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D18 · Solution Shape9.2 / 10Exemplary✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Documented

111 projects, 894 source files, 53351 hand-written lines of code (35752 production / 17599 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 141 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 202 inter-project edges.

Thin analysable surface across projects: ViennaNET.Orm.DB2.Lnx.DefaultConfiguration · ×14src/ViennaNET.Orm.DB2.Lnx.DefaultConfiguration/ViennaNET.Orm.DB2.Lnx.DefaultConfiguration.csproj

✓ On the Gold path — maintain.

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 project's READMEs are well written: each directory's README is a focused document that explains what it contains (e.g. 'Сборка, содержащая реализацию посредника для выполнения операций сервисов' for the Mediator directory), and every visible section in the body of the documents appears in the outline; there are no missing-overview or missing-architecture docs. The XML-doc coverage is strong (e.g. 100% for ViennaNET.Mediator.Pipelines, ViennaNET.WebApi.Configurators.HttpClients.Jwt) but this reflects documentation quality rather than a defect. The repository's READMEs are strong in describing what each directory provides and showing usage examples for the directories they document. The MQSeriesQueue README is a good class-documentation example (MqSeriesQueueConfiguration, MqSeriesQueueMessageAdapterConstructor), but it does not show how to run the assembly or where to find the configuration file's queueString field described in detail. (14 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)

Documentation: no usage examplessrc/ViennaNET.Messaging.MQSeriesQueue/README.md

XML-doc coverage: ViennaNET.WebApi · ×84src/ViennaNET.WebApi/ViennaNET.WebApi.csproj

What to do

Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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?

D24 · Comment ValueStrong◐ Sampled · advisory

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.

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

32 valuable / 0 redundant across 200 sampled comments.

What to do

Improve Comment Value — currently 7.7/10. — 32 valuable / 0 redundant across 200 sampled comments.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion10.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 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 116 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

D27 · Navigability8.6 / 10Strong✓ Tool-verified

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

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

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

Pass-through layersrc/ViennaNET.Validation/Validators/RulesValidatorAsync.cs:10

What to do

Resolve the 1 Pass-through layer finding(s) in Navigability — start with RulesValidatorAsync.cs. — One of this dimension's main actionable groups (1 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)8.0 / 10Adequategated by 2 critical findings✓ 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 8.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

What to do

Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)3.7 / 10Weak✓ 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 3.7 / 10 · rule-coverage 100% · ceiling Documented

23 finding(s): 0 critical, 14 high, 9 medium, 0 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

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

What to do

Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 11 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (11 issue-level, 0 of them charged here).

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

25 finding(s): 2 critical, 16 high, 7 medium, 0 low.

REDACTED

What to do

Resolve the 16 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (16 issue-level).
Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-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

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

Orphaned file · ×169src/ViennaNET.Validation/Rules/FluentRule/CurrentValidatorHolderExtensions.cs:1

Most significant orphaned file · ×3src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs:1

Dormant codebase

What to do

Resolve the 169 Orphaned file finding(s) in Knowledge Freshness — start with Mediator.cs (2), IMediator.cs (2), CurrentValidatorHolderExtensions.cs. — One of this dimension's main actionable groups (169 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with CustomRollingFileAppender.cs, IRedisDatabase.cs, RedisDatabase.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?

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

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

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified

Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.

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

2 of 2157 first-party methods have an oversized IL body.

IL efficiency: 2 authored method(s) exceed the IL budgetsrc/ViennaNET.ArcSight/Validation/ExtensionsRule.cs:7

✓ On the Gold path — maintain.

Detailed fixes: d39_recommendation.md · top locations in Appendix A, every location in findings.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 117 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 composition7.1 / 10Strong✓ 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.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

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 ViennaNET.Validation.Rules ↔ ViennaNET.Validation.Rules.ValidationResults ↔ ViennaNET.Validation.ValidationChains ↔ ViennaNET.Validation.Validators depend on each other. The lightest dependency in the cycle is ViennaNET.Validation.Rules → ViennaNET.Validation.Validators (ViennaNET.Validation.Rules.IMessageValidation → ViennaNET.Validation.Validators.ValidationResult, 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/ViennaNET.Validation/Rules/IMessageValidation.cs:1
The namespaces ViennaNET.Orm ↔ ViennaNET.Orm.Application ↔ ViennaNET.Orm.DI ↔ ViennaNET.Orm.Factories ↔ ViennaNET.Orm.Repositories depend on each other. The lightest dependency in the cycle is ViennaNET.Orm.DI → ViennaNET.Orm (ViennaNET.Orm.DI.ISessionManagerProvider → ViennaNET.Orm.ISessionManager, 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/ViennaNET.Orm/DI/ISessionManagerProvider.cs:7
The namespaces ViennaNET.Logging ↔ ViennaNET.Logging.Configuration ↔ ViennaNET.Logging.Contracts depend on each other. The lightest dependency in the cycle is ViennaNET.Logging.Configuration → ViennaNET.Logging (ViennaNET.Logging.Configuration.FluentConfiguration → ViennaNET.Logging.LogLevel, 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/ViennaNET.Logging/Configuration/FluentConfiguration.cs:7

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.

`IRedisDatabase` declares 48 members: `ObjectGet`, `ObjectGet`, `HashObjectGet`, `HashObjectGet`, `HashObjectGetAll`, `ObjectSet`, `ObjectSet`, `ObjectSet`, `HashObjectSet`, `HashObjectSet`, `ObjectGetAsync`, `ObjectGetAsync`, `HashObjectGetAsync`, `HashObjectGetAsync`, `HashObjectGetAllAsync`, `ObjectSetAsync`, `ObjectSetAsync`, `ObjectSetAsync`, `HashObjectSetAsync`, `HashObjectSetAsync`, `StringGet`, `StringGet`, `HashStringGet`, `HashStringGet`, `HashStringGetAll`, `StringSet`, `StringSet`, `StringSet`, `HashStringSet`, `HashStringSet`, `StringGetAsync`, `StringGetAsync`, `HashStringGetAsync`, `HashStringGetAsync`, `HashStringGetAllAsync`, `StringSetAsync`, `StringSetAsync`, `StringSetAsync`, `HashStringSetAsync`, `HashStringSetAsync`, and 8 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 48 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 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/ViennaNET.Redis/IRedisDatabase.cs:12
`IRedisServer` declares 22 members: `IsConnected`, `EndPoint`, `ServerType`, `Version`, `IsSlave`, `Keys`, `Save`, `SaveAsync`, `ConfigGet`, `ConfigGetAsync`, `ConfigSet`, `ConfigSetAsync`, `Info`, `InfoAsync`, `LastSave`, `LastSaveAsync`, `Time`, `TimeAsync`, `FlushAllDatabases`, `FlushAllDatabasesAsync`, `FlushDatabase`, `FlushDatabaseAsync`. 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/ViennaNET.Redis/IRedisServer.cs:13
`ISilentRedisServer` declares 22 members: `IsConnected`, `EndPoint`, `ServerType`, `Version`, `IsSlave`, `Keys`, `Save`, `SaveAsync`, `ConfigGet`, `ConfigGetAsync`, `ConfigSet`, `ConfigSetAsync`, `Info`, `InfoAsync`, `LastSave`, `LastSaveAsync`, `Time`, `TimeAsync`, `FlushAllDatabases`, `FlushAllDatabasesAsync`, `FlushDatabase`, `FlushDatabaseAsync`. 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/ViennaNET.Redis/ISilentRedisServer.cs:13
`IWorkSheet` declares 20 members: `Name`, `this[]`, `Visible`, `Rows`, `HideColumn`, `ShowColumn`, `ColumnHidden`, `GetColumnWidth`, `CopyStyles`, `SetColumnWidth`, `ShiftDownRow`, `RecalculateFormulas`, `HideRow`, `ReadCellByName`, `CreateVerticalRange`, `CreateRange`, `CreateHierarchicalRange`, `MergeCells`, `CreateStyle`, `CreateStyle`. 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 20 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 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/ViennaNET.Excel/Contracts/IWorkSheet.cs:5
`ICompanyHostBuilder` declares 25 members: `BuildWebHost`, `AddMvcBuilderConfiguration`, `AddMvcOptionsConfiguration`, `ConfigureApp`, `AddMiddleware`, `ConfigureContainer`, `ConfigureContainer`, `InitializeContainer`, `RegisterServices`, `RegisterServices`, `CreateContainer`, `VerifyContainer`, `UseServer`, `AddOnStartAction`, `AddOnStartAction`, `AddOnStoppingAction`, `AddOnStoppingAction`, `AddOnStoppedAction`, `AddOnStoppedAction`, `AddExceptionHandler`, `AddExceptionHandler`, `AddExceptionHandler`, `AddExceptionHandler`, `RegisterHostBuilderAction`, `RegisterConfigurationBuilderAction`. 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 25 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/ViennaNET.WebApi.Abstractions/ICompanyHostBuilder.cs:13

What to do

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

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

C1 · Data Protection3.0 / 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.

No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

What to do

Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).

Do you agree with this assessment?

C2 · Access Controls3.0 / 10Weak✓ Tool-verified

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.

Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.

What to do

Enforce authorization at every handler — call the guard method (throw-on-violation) from each one, or adopt [Authorize] so protected-by-default is demonstrable.

Do you agree with this assessment?

C4 · Data Retention6.5 / 10Adequate✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.

What to do

Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.

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. (×11) — src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:125, src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:130, src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:221, …

What to do

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs8.2 / 10Strong✓ 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.

`ExecuteFuture` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:59
`ExecuteFutureValue` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:64
`SetResultTransformerAndAdditionalCriteria` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:69
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×2) — src/ViennaNET.Excel/Impls/NPoiExcelFile.cs:199, src/ViennaNET.Logging/Log4NetImpl/Log4NetConfigurationApplier.cs:168

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.9 / 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 61 of 116 project(s) that lack one — worth up to 1.1 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 structure10.0 / 10Exemplary✓ 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.

Do you agree with this assessment?

M4 · Documentation accuracy2.0 / 10Critical◐ 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.

README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:4
src/ViennaNET.Extensions.Configuration.HashicorpVault/README.md installs the package `ViennaNET.Extensions.Configuration.HashicorpVault` (`dotnet add package ViennaNET.Extensions.Configuration.HashicorpVault`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/ViennaNET.Extensions.Configuration.HashicorpVault/README.md:23
src/ViennaNET.Extensions.Http/README.md installs the package `ViennaNET.Extensions.Http` (`dotnet add package ViennaNET.Extensions.Http`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/ViennaNET.Extensions.Http/README.md:31
src/ViennaNET.KasperskyScanEngine.Client/README.md installs the package `ViennaNET.KasperskyScanEngine.Client` (`dotnet add package ViennaNET.KasperskyScanEngine.Client`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/ViennaNET.KasperskyScanEngine.Client/README.md:25

What to do

Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests; src/ViennaNET.Extensions.Configuration.HashicorpVault/README.md installs the package `ViennaNET.Extensions.Configuration.HashicorpVault` (`dotnet add package ViennaNET.Extensions.Configuration.HashicorpVault`), but no project or props file references it; src/ViennaNET.Extensions.Http/README.md installs the package `ViennaNET.Extensions.Http` (`dotnet add package ViennaNET.Extensions.Http`), but no project or props file references it; src/ViennaNET.KasperskyScanEngine.Client/README.md installs the package `ViennaNET.KasperskyScanEngine.Client` (`dotnet add package ViennaNET.KasperskyScanEngine.Client`), but no project or props file references it.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P2 · Observability7.7 / 10Strong✓ 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 28/50 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 50, 5 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.
Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.

Do you agree with this assessment?

P3 · Security & performance tooling4.0 / 10Weak✓ 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.

What to do

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?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ 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.

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.

`services .Configure<JsonSerializerOptions>(IKasperskyScanEngineApi.JsonSerial...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/ViennaNET.KasperskyScanEngine.Client/DependencyInjection/KseServiceCollectionExtensions.cs:34
`services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×4) — src/ViennaNET.WebApi.Configurators.HttpClients.Basic/BasicHttpClientsConfigurator.cs:41, src/ViennaNET.WebApi.Configurators.HttpClients.Jwt/JwtHttpClientsConfigurator.cs:35, src/ViennaNET.WebApi.Configurators.HttpClients.NoAuthentication/NoAuthenticationHttpClientsConfigurator.cs:37, …

What to do

Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.

Do you agree with this assessment?

PF3 · Async & latency hygiene6.0 / 10Adequate✓ 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.

3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×3) — src/ViennaNET.Messaging/Processing/Impl/Polling.cs:129, src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:431, src/ViennaNET.Extensions.Configuration.HashicorpVault/VaultConfigurationProvider.cs:54

What to do

Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().

Do you agree with this assessment?

S1 · Web-Security Posture8.0 / 10Strong✓ 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.

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. — src/ViennaNET.WebApi/CompanyHostBuilder.cs:68

What to do

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.

Do you agree with this assessment?

X1 · Async correctness7.1 / 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.

This blocks on a Task **while holding a `lock`**, which is worse than an ordinary sync-over-async in two ways. `await` is illegal inside a `lock` body, so the usual fix — make the caller `async` and await it — cannot be applied where this block stands. And the thread parks while still holding the lock, so it occupies the critical section doing no work: every other caller serialises behind an operation that is only waiting, and if the awaited task itself needs a thread the pool has run out of, they wait forever. Do the async work OUTSIDE the critical section: take the lock only to read the shared state, release it, await the call, then re-take the lock to publish the result — re-checking on re-entry whether another caller won the race and, if so, discarding your result rather than overwriting theirs. Where the critical section genuinely has to span the async call, `lock` is the wrong primitive: use an async-aware one (`SemaphoreSlim` with `await WaitAsync()`) so waiters yield their thread instead of parking it. — src/ViennaNET.Messaging/Processing/Impl/Polling.cs:129
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. — src/ViennaNET.Messaging/Sending/Impl/MessageSender.cs:77
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. (×2) — src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:431, src/ViennaNET.Extensions.Configuration.HashicorpVault/VaultConfigurationProvider.cs:54

What to do

Blocking wait while holding a `lock`

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 correctness5.0 / 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.

`ScopeLogRedirector` declares a finalizer (line 49), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Logging/ScopeLogRedirector.cs:49
`ExplicitNhSessionScope` declares a finalizer (line 53), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Orm/Factories/ExplicitNhSessionScope.cs:53
`UnitOfWork` declares a finalizer (line 149), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Orm/Repositories/UnitOfWork.cs:149
`_syslogMessageSender` is never created by `CefSender` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 32). Its declared type `ISyslogMessageSender` 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/ViennaNET.ArcSight/CefSender.cs:32
`QueuePollingReactorBase` declares a finalizer (line 285), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs:285
`_adapter` is never created by `QueuePollingReactorBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 129). Its declared type `IMessageAdapter` 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/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs:129
`Polling` declares a finalizer (line 144), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Messaging/Processing/Impl/Polling.cs:144
`QueueSubscribedReactorBase` declares a finalizer (line 313), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Messaging/Processing/Impl/Subscribe/QueueSubscribedReactorBase.cs:313
`adapter` is never created by `QueueSubscribedReactorBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 140). Its declared type `IMessageAdapterWithSubscribing` 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/ViennaNET.Messaging/Processing/Impl/Subscribe/QueueSubscribedReactorBase.cs:140
`MqSeriesQueueMessageAdapter` declares a finalizer (line 198), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:198
`ActiveMqQueueMessageAdapter` declares a finalizer (line 211), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:211

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.2 / 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 37/102 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/ViennaNET.HttpClient/HttpResponseMessageExtensions.cs:41, src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:122, src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:130, …

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 materialisation10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

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 enumerated7.6 / 10Strong✓ Tool-verified

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.

`log4netWrapper._logs` is enumerated directly, and line 48 calls `log4netWrapper._logs.Add(…)` inside the loop body — a structural change to a `Dictionary`. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen. — src/ViennaNET.Logging/Log4NetImpl/Log4NetWrapper.cs:44

What to do

Each finding names the two spans that cannot both stand — the `foreach` source, and the call inside the body that structurally changes that same collection. Confirm from those two, then pick one: enumerate a snapshot (`foreach (var x in c.ToList())`), collect what needs changing and apply it after the loop, or — where the loop was only ever meant to act on the first match — `break` immediately after the mutation, which is the one shape that is already safe.

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 handling7.0 / 10Strong✓ 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. (×4) — src/ViennaNET.Logging/Logger.cs:31, src/ViennaNET.Word/Document.cs:407, src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs:83, …
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). — src/ViennaNET.Logging/ScopeLogRedirector.cs:39

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 logging6.4 / 10Adequate✓ 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. (×12) — src/ViennaNET.Logging/LogAutoStopWatch.cs:37, src/ViennaNET.Mediator/Collectors/EventCollector.cs:107, src/ViennaNET.Mediator/Collectors/EventCollector.cs:119, …

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types9.9 / 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.

This method contradicts itself about `exception`: line 91 writes `exception?.GetType`, which says `exception` can be null, but line 100 then dereferences it directly as `exception.Message` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/ViennaNET.WebApi/CompanyHostBuilderErrorHandler.cs:100
~0.1 `!` suppressions per 1k syntax nodes — 9 suppression(s) across the 126529 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Do you agree with this assessment?

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	71%	Strong	Solid.
Architecture	91%	Exemplary	Strongest area.
Maturity	34%	Weak — gated by D34, M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	42%	Weak — gated by D12, P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	44%	Weak — gated by D29, D30, D36, C1, C2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Acceptable, with room to improve.

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

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

P12 CI test-gate honesty — 3 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 3 control(s) we could not find positive evidence for

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

C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 36 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 user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
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
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 'ViennaNET.WebApi.Abstractions.csproj'`: Unable to proceed with project 'src/ViennaNET.WebApi.Abstractions/ViennaNET.WebApi.Abstractions.csproj'. Ensure you have a runnable project type. A…; runtime evidence skipped (launch chosen because src/ViennaNET.WebApi.Abstractions/ViennaNET.WebApi.Abstractions.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.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
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) — 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.
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
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Handler temporal coupling — no event handlers detected — temporal-coupling check not applicable
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 — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an append-only event-store seam (IEventStore/Append-of-events))
P8 Schema migrations — no EF Core usage detected
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
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
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 — 55 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×16

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D12 · Dependency Hygiene · Vulnerable · ×7

Vulnerable: log4net — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: NHibernate — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: System.Text.Json — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Npgsql — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Apache.NMS.ActiveMQ — REDACTED — Critical severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: Apache.NMS.AMQP — REDACTED — Critical severity. https://github.com/advisories/[GHSA redacted]
Vulnerable: KubernetesClient — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]

D17 · Explicit Debt · WriteOnlyPrivateField · ×5

WriteOnlyPrivateField src/ViennaNET.Excel/Impls/NPoiExcelFile.cs:36 — private IFileUtils _utils — 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/ViennaNET.Messaging/Processing/Impl/Polling.cs:18 — private int _timeoutPollingQueue — 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/ViennaNET.Orm/Repositories/CommandExecutor.cs:14 — private ILogger _logger — 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/ViennaNET.Orm/Repositories/EntityRepository.cs:18 — private ILogger _logger — 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 tests/ViennaNET.Messaging.Tests/DSL/MessageAdapterBuilder.cs:12 — private MessageProcessingType? _processingType — 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 · EmptyCatchBlock · ×5

EmptyCatchBlock src/ViennaNET.Excel/Impls/NPoiExcelProvider.cs:83 — 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/ViennaNET.Excel/Impls/NPoiExcelProvider.cs:125 — 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/ViennaNET.Logging/Logger.cs:31 — 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/ViennaNET.Logging/ScopeLogRedirector.cs:39 — 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/ViennaNET.Word/Document.cs:407 — 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.

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

Namespace dependency cycle src/ViennaNET.Validation/Rules/IMessageValidation.cs:1 — The namespaces ViennaNET.Validation.Rules ↔ ViennaNET.Validation.Rules.ValidationResults ↔ ViennaNET.Validation.ValidationChains ↔ ViennaNET.Validation.Validators depend on each other. The lightest dependency in the cycle is ViennaNET.Validation.Rules → ViennaNET.Validation.Validators (ViennaNET.Validation.Rules.IMessageValidation → ViennaNET.Validation.Validators.ValidationResult, 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/ViennaNET.Orm/DI/ISessionManagerProvider.cs:7 — The namespaces ViennaNET.Orm ↔ ViennaNET.Orm.Application ↔ ViennaNET.Orm.DI ↔ ViennaNET.Orm.Factories ↔ ViennaNET.Orm.Repositories depend on each other. The lightest dependency in the cycle is ViennaNET.Orm.DI → ViennaNET.Orm (ViennaNET.Orm.DI.ISessionManagerProvider → ViennaNET.Orm.ISessionManager, 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/ViennaNET.Logging/Configuration/FluentConfiguration.cs:7 — The namespaces ViennaNET.Logging ↔ ViennaNET.Logging.Configuration ↔ ViennaNET.Logging.Contracts depend on each other. The lightest dependency in the cycle is ViennaNET.Logging.Configuration → ViennaNET.Logging (ViennaNET.Logging.Configuration.FluentConfiguration → ViennaNET.Logging.LogLevel, 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.

D28 · Secrets (history) · REDACTED · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×2

REDACTED
REDACTED

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

REDACTED

X1 · Async correctness · Blocking wait while holding a `lock` · ×1

Blocking wait while holding a `lock` src/ViennaNET.Messaging/Processing/Impl/Polling.cs:129 — This blocks on a Task **while holding a `lock`**, which is worse than an ordinary sync-over-async in two ways. `await` is illegal inside a `lock` body, so the usual fix — make the caller `async` and await it — cannot be applied where this block stands. And the thread parks while still holding the lock, so it occupies the critical section doing no work: every other caller serialises behind an operation that is only waiting, and if the awaited task itself needs a thread the pool has run out of, they wait forever. Do the async work OUTSIDE the critical section: take the lock only to read the shared state, release it, await the call, then re-take the lock to publish the result — re-checking on re-entry whether another caller won the race and, if so, discarding your result rather than overwriting theirs. Where the critical section genuinely has to span the async call, `lock` is the wrong primitive: use an async-aware one (`SemaphoreSlim` with `await WaitAsync()`) so waiters yield their thread instead of parking it.

Serious — 215 finding(s)

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

Async method without CancellationToken: HandleAsync src/ViennaNET.HttpClient/HttpResponseMessageExtensions.cs:41 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:122 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:130 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:139 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashObjectGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:147 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashObjectGetAllAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:156 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:164 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:175 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:186 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:202 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashObjectSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:213 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:305 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:312 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashStringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:319 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashStringGetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:326 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashStringGetAllAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:334 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:341 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:351 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:361 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashStringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:369 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HashStringSetAsync src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs:379 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs:128 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConfigGetAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs:157 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConfigSetAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs:186 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InfoAsync src/ViennaNET.Redis/Implementation/Silent/SilentRedisServer.cs:216 — No CancellationToken parameter — this work can't be stopped early once started.
+ 14 more in this group — see findings.md.

D17 · Explicit Debt · ObsoleteWithCallers · ×22

ObsoleteWithCallers src/ViennaNET.Excel/IO/IFileUtils.cs:7 — [Obsolete] IFileUtils
ObsoleteWithCallers src/ViennaNET.Logging/Logger.cs:16 — [Obsolete] Logger
ObsoleteWithCallers src/ViennaNET.Mediator/Collectors/EventCollector.cs:12 — [Obsolete] EventCollector
ObsoleteWithCallers src/ViennaNET.Mediator/Collectors/EventCollectorFactory.cs:7 — [Obsolete] EventCollectorFactory
ObsoleteWithCallers src/ViennaNET.Mediator/Exceptions/ExecuteCommandException.cs:10 — [Obsolete] ExecuteCommandException
ObsoleteWithCallers src/ViennaNET.Mediator/Exceptions/PublishEventException.cs:10 — [Obsolete] PublishEventException
ObsoleteWithCallers src/ViennaNET.Mediator/Exceptions/SendRequestException.cs:10 — [Obsolete] SendRequestException
ObsoleteWithCallers src/ViennaNET.Mediator/Exceptions/UnsupportedTypeMessageException.cs:10 — [Obsolete] UnsupportedTypeMessageException
ObsoleteWithCallers src/ViennaNET.Mediator/ICommand.cs:8 — [Obsolete] ICommand
ObsoleteWithCallers src/ViennaNET.Mediator/IMediator.cs:10 — [Obsolete] IMediator
ObsoleteWithCallers src/ViennaNET.Mediator/IMessageHandler.cs:8 — [Obsolete] IMessageHandler
ObsoleteWithCallers src/ViennaNET.Mediator/IMessageHandler.cs:17 — [Obsolete] IMessageHandler
ObsoleteWithCallers src/ViennaNET.Mediator/IMessageHandler.cs:34 — [Obsolete] IMessageHandler
ObsoleteWithCallers src/ViennaNET.Mediator/IMessageHandlerAsync.cs:10 — [Obsolete] IMessageHandlerAsync
ObsoleteWithCallers src/ViennaNET.Mediator/IMessageHandlerAsync.cs:19 — [Obsolete] IMessageHandlerAsync
ObsoleteWithCallers src/ViennaNET.Mediator/IMessageHandlerAsync.cs:38 — [Obsolete] IMessageHandlerAsync
ObsoleteWithCallers src/ViennaNET.Mediator/IMessageRecipientsRegistrar.cs:6 — [Obsolete] IMessageRecipientsRegistrar
ObsoleteWithCallers src/ViennaNET.Mediator/IPipelineProcessorsRegistrar.cs:6 — [Obsolete] IPipelineProcessorsRegistrar
ObsoleteWithCallers src/ViennaNET.Mediator/IRequest.cs:8 — [Obsolete] IRequest
ObsoleteWithCallers src/ViennaNET.Mediator/Mediators/Mediator.cs:19 — [Obsolete] Mediator
ObsoleteWithCallers src/ViennaNET.Mediator/Pipeline/IPreProcessorService.cs:8 — [Obsolete] IPreProcessorService
ObsoleteWithCallers src/ViennaNET.Mediator/Pipeline/PreProcessorService.cs:12 — [Obsolete] PreProcessorService

D17 · Explicit Debt · CoverageExclusion · ×16

CoverageExclusion src/ViennaNET.Logging/DefaultCategoryLogger.cs:10 — class DefaultCategoryLogger — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Logging/Log4NetImpl/CategoryLogger.cs:10 — class CategoryLogger — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Logging/Logging.cs:9 — class Logging — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.ActiveMQQueue.DefaultConfiguration/ActiveMqPackage.cs:11 — class ActiveMqPackage — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.DefaultConfiguration/ContainerExtensions.cs:19 — class ContainerExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:195 — method ProducerErrorHandler — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:210 — method ProducerLogHandler — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:222 — method ConsumerErrorHandler — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:237 — method ConsumerLogHandler — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueSubscribingMessageAdapter.cs:30 — method Reply — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueSubscribingMessageAdapter.cs:42 — method RequestAndWaitResponse — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging.RabbitMQQueue/RabbitMqConnectionFactory.cs:7 — class RabbitMqConnectionFactory — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Messaging/Listening/QueueListener.cs:9 — class QueueListener — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.Redis/Implementation/Default/RedisDatabaseProvider.cs:13 — class RedisDatabaseProvider — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.WebApi.Configurators.Diagnostic/CompanyDiagnosticConfigurator.cs:15 — class CompanyDiagnosticConfigurator — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
CoverageExclusion src/ViennaNET.WebApi.WindowsHosting/WindowsHostingExtensions.cs:12 — class WindowsHostingExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.

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

Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:125 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:130 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:221 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:226 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:231 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:236 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:242 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/EntityFactoryServiceStubBuilder.cs:248 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:59 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:64 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:69 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

X18 · Disposal-pattern correctness · Finalizer on a type that owns no unmanaged resource · ×8

Finalizer on a type that owns no unmanaged resource src/ViennaNET.Logging/ScopeLogRedirector.cs:49 — `ScopeLogRedirector` declares a finalizer (line 49), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/ViennaNET.Orm/Factories/ExplicitNhSessionScope.cs:53 — `ExplicitNhSessionScope` declares a finalizer (line 53), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/ViennaNET.Orm/Repositories/UnitOfWork.cs:149 — `UnitOfWork` declares a finalizer (line 149), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs:285 — `QueuePollingReactorBase` declares a finalizer (line 285), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/ViennaNET.Messaging/Processing/Impl/Polling.cs:144 — `Polling` declares a finalizer (line 144), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/ViennaNET.Messaging/Processing/Impl/Subscribe/QueueSubscribedReactorBase.cs:313 — `QueueSubscribedReactorBase` declares a finalizer (line 313), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:198 — `MqSeriesQueueMessageAdapter` declares a finalizer (line 198), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:211 — `ActiveMqQueueMessageAdapter` declares a finalizer (line 211), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.

D30 · Dependency Vulnerabilities · Medium CVE · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D12 · Dependency Hygiene · Deprecated · ×6

Deprecated: App.Metrics.AspNetCore.Mvc src/ViennaNET.WebApi/ViennaNET.WebApi.csproj:8 — App.Metrics.AspNetCore.Mvc 4.3.0 — Legacy
Deprecated: App.Metrics.Formatters.Prometheus src/ViennaNET.WebApi/ViennaNET.WebApi.csproj:9 — App.Metrics.Formatters.Prometheus 4.3.0 — Legacy
Deprecated: Microsoft.IdentityModel.Tokens src/ViennaNET.Security.Jwt/ViennaNET.Security.Jwt.csproj:9 — Microsoft.IdentityModel.Tokens 7.5.1 — Legacy
Deprecated: System.IdentityModel.Tokens.Jwt src/ViennaNET.Security.Jwt/ViennaNET.Security.Jwt.csproj:10 — System.IdentityModel.Tokens.Jwt 7.5.1 — Legacy
Deprecated: NPOI REDACTED:9 — NPOI 2.6.2 — Legacy
Deprecated: System.Data.SQLite REDACTED:8 — System.Data.SQLite 1.0.118 — CriticalBugs

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · BareSuppressMessage · ×5

BareSuppressMessage src/ViennaNET.Extensions.Mediator/DependencyInjection/MediatorServiceCollectionExtensions.cs:39 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ViennaNET.Extensions.Mediator/DependencyInjection/MediatorServiceCollectionExtensions.cs:117 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ViennaNET.Extensions.Mediator/Mediator.cs:7 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ViennaNET.Extensions.Mediator/Mediator.cs:27 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ViennaNET.KasperskyScanEngine.Client/Models/ScanRequestBase.cs:15 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×5

Outbound HTTP without resilience src/ViennaNET.KasperskyScanEngine.Client/DependencyInjection/KseServiceCollectionExtensions.cs:34 — `services .Configure<JsonSerializerOptions>(IKasperskyScanEngineApi.JsonSerial...` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.Basic/BasicHttpClientsConfigurator.cs:41 — `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.Jwt/JwtHttpClientsConfigurator.cs:35 — `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.NoAuthentication/NoAuthenticationHttpClientsConfigurator.cs:37 — `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/ViennaNET.WebApi.Configurators.HttpClients.Ntlm/NtlmHttpClientsConfigurator.cs:29 — `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).

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

Swallowed exception (empty catch) src/ViennaNET.Logging/Logger.cs:31 — 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/ViennaNET.Logging/ScopeLogRedirector.cs:39 — 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/ViennaNET.Word/Document.cs:407 — 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/ViennaNET.Excel/Impls/NPoiExcelProvider.cs:83 — 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/ViennaNET.Excel/Impls/NPoiExcelProvider.cs:125 — 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.

D3 · God Classes · TooManyMethods · ×4

TooManyMethods: RedisDatabase src/ViennaNET.Redis/Implementation/Default/RedisDatabase.cs — TooManyMethods — 356 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: SilentRedisDatabase src/ViennaNET.Redis/Implementation/Silent/SilentRedisDatabase.cs — TooManyMethods — 150 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× 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: CompanyHostBuilder src/ViennaNET.WebApi/CompanyHostBuilderActions.cs — TooManyMethods — 191 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods, declared across 3 files: ViennaNET.WebApi/CompanyHostBuilderActions.cs (20), ViennaNET.WebApi/CompanyHostBuilder.cs (7), ViennaNET.WebApi/CompanyHostBuilderErrorHandler.cs (5). The bar is 30 methods; this is 2 over it, 1.07× 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: Logger src/ViennaNET.Logging/Logger.cs — TooManyMethods — 113 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4

Duplicated block (5 lines × 2) src/ViennaNET.Validation/Validators/IValidatorExtensions.cs:88 — src/ViennaNET.Validation/Validators/IValidatorExtensions.cs:88-92 | src/ViennaNET.Validation/Validators/IValidatorExtensionsAsync.cs:91-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/ViennaNET.Validation/Validators/IValidatorExtensions.cs:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/ViennaNET.Validation/Rules/FluentRule/BaseFluentRule.cs:45 — src/ViennaNET.Validation/Rules/FluentRule/BaseFluentRule.cs:45-49 | src/ViennaNET.Validation/Rules/FluentRule/BaseFluentRuleAsync.cs:52-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:269 — src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:269-273 | src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:458-462 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/ViennaNET.Extensions.Configuration.HashicorpVault/Internals/ConfigurationPathUtils.cs:18 — src/ViennaNET.Extensions.Configuration.HashicorpVault/Internals/ConfigurationPathUtils.cs:18-22 | src/ViennaNET.Extensions.Configuration.Kubernetes/KubernetesConfigurationProvider.cs:124-128 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `key` to `this string` in one and `string` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D5 · Coupling · Off the main sequence · ×4

Off the main sequence: ViennaNET.Orm.DB2.NHibernateDriver REDACTED:1 — ViennaNET.Orm.DB2.NHibernateDriver: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: ViennaNET.Utils src/ViennaNET.Utils/ViennaNET.Utils.csproj:1 — ViennaNET.Utils: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 21 project(s), so it's rigid to change.
Off the main sequence: ViennaNET.HttpClient src/ViennaNET.HttpClient/ViennaNET.HttpClient.csproj:1 — ViennaNET.HttpClient: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: ViennaNET.Messaging.DefaultConfiguration src/ViennaNET.Messaging.DefaultConfiguration/ViennaNET.Messaging.DefaultConfiguration.csproj:1 — ViennaNET.Messaging.DefaultConfiguration: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.

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

Sync-over-async blocking — 3 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/ViennaNET.Messaging/Processing/Impl/Polling.cs:129 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:431 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/ViennaNET.Extensions.Configuration.HashicorpVault/VaultConfigurationProvider.cs:54 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).

D3 · God Classes · MethodTooLong · ×3

MethodTooLong: ExtensionsRule.ExtensionsRule(…) src/ViennaNET.ArcSight/Validation/ExtensionsRule.cs:7 — MethodTooLong — ExtensionsRule(…) runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CefMessageSerializer.Serialize src/ViennaNET.ArcSight/CefMessageSerializer.cs:201 — MethodTooLong — Serialize runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CefMessageSerializer.CefMessageSerializer(…) src/ViennaNET.ArcSight/CefMessageSerializer.cs:21 — MethodTooLong — CefMessageSerializer(…) runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

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

Duplicated block (8 lines × 2) src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/InclusiveBetweenValidator.cs:13 — src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/InclusiveBetweenValidator.cs:13-20 | src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/InclusiveBetweenValidatorAsync.cs:14-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:258 — src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:258-265 | src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:444-454 — 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 (8 lines × 2) src/ViennaNET.WebApi.Configurators.Security.Jwt/JwtGenerationConfigurator.cs:26 — src/ViennaNET.WebApi.Configurators.Security.Jwt/JwtGenerationConfigurator.cs:26-33 | src/ViennaNET.WebApi.Configurators.Security.Jwt/JwtSecurityConfigurator.cs:99-106 — 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.

IC1 · Incompleteness & stubs · Unfinished stub · ×3

Unfinished stub — throws NotImplementedException src/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:59 — `ExecuteFuture` 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/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:64 — `ExecuteFutureValue` 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/ViennaNET.TestUtils.Orm/NhQueryable/NhQueryProviderProxy.cs:69 — `SetResultTransformerAndAdditionalCriteria` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.

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

Disposes a dependency it does not own src/ViennaNET.ArcSight/CefSender.cs:32 — `_syslogMessageSender` is never created by `CefSender` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 32). Its declared type `ISyslogMessageSender` 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/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs:129 — `_adapter` is never created by `QueuePollingReactorBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 129). Its declared type `IMessageAdapter` 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/ViennaNET.Messaging/Processing/Impl/Subscribe/QueueSubscribedReactorBase.cs:140 — `adapter` is never created by `QueueSubscribedReactorBase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 140). Its declared type `IMessageAdapterWithSubscribing` 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.

D10 · Test Quality · Skipped test · ×2

Skipped test: CefSender_SendCef tests/ViennaNET.ArcSight.Tests/Integration/TestClient.cs:9 — Skipped — [Explicit]
Skipped test: CreateTest tests/ViennaNET.Word.Tests/WordDocumentFactoryTests.cs:18 — Skipped — [Explicit]

D10 · Test Quality · No assertions · ×2

No assertions: ConcurrentSendMessageAsyncTest tests/ViennaNET.Mediator.Tests/Units/Mediators/MediatorTests.cs:278 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: WhenRuleSet_DifferentData_CorrectResults tests/ViennaNET.Validation.Tests/WhenClauseTests.cs:80 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.

D17 · Explicit Debt · TodoComment · ×2

TodoComment src/ViennaNET.ArcSight/SyslogRfc3164MessageSerializer.cs:8 — //TODO: remove when https://github.com/emertechie/SyslogNet/pull/17 will be merged
TodoComment src/ViennaNET.WebApi/CompanyHostBuilder.cs:128 — // 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.

D17 · Explicit Debt · BarePragmaDisable · ×2

BarePragmaDisable src/ViennaNET.Extensions.Http/ClientOptionsBase.cs:21 — #pragma warning disable CS8618 — 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.
BarePragmaDisable src/ViennaNET.KasperskyScanEngine.Client/Models/ScanRequestBase.cs:16 — #pragma warning disable S1694 — 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.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

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

Duplicated block (13 lines × 2) src/ViennaNET.Messaging.ActiveMQQueue/ActiveMqQueueMessageConverter.cs:91 — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMqQueueMessageConverter.cs:91-103 | src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageConverter.cs:39-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:196 — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:196-208 | src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:172-184 — before extracting anything, compare `src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs` and `src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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 (9 lines × 2) · ×2

Duplicated block (9 lines × 2) src/ViennaNET.Word/Document.cs:130 — src/ViennaNET.Word/Document.cs:130-138 | src/ViennaNET.Word/Document.cs:174-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/ViennaNET.WebApi.Configurators.HttpClients.Jwt/JwtHttpClientsConfigurator.cs:29 — src/ViennaNET.WebApi.Configurators.HttpClients.Jwt/JwtHttpClientsConfigurator.cs:29-37 | src/ViennaNET.WebApi.Configurators.HttpClients.NoAuthentication/NoAuthenticationHttpClientsConfigurator.cs:31-39 — 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 (7 lines × 2) · ×2

Duplicated block (7 lines × 2) src/ViennaNET.Word/WordprocessingDocumentFactory.cs:17 — src/ViennaNET.Word/WordprocessingDocumentFactory.cs:17-23 | src/ViennaNET.Word/WordprocessingDocumentFactory.cs:29-35 — 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/ViennaNET.Word/WordprocessingDocumentFactory.cs:17` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (7 lines × 2) src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:173 — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:173-179 | src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:160-166 — before extracting anything, compare `src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs` and `src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `additionalParameters` to `string Value)[]` in one and `params (string Name, string Value)[]` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

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

Duplicated block (12 lines × 2) src/ViennaNET.Orm/Conventions/IntToString.cs:14 — src/ViennaNET.Orm/Conventions/IntToString.cs:14-25 | src/ViennaNET.Orm/Conventions/StringToEnum.cs:22-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (12 lines × 2) src/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs:170 — src/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs:170-181 | src/ViennaNET.Messaging/Processing/Impl/Subscribe/QueueSubscribedReactor.cs:46-57 — 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.

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

Sync-over-async (deadlock risk) src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:431 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/ViennaNET.Extensions.Configuration.HashicorpVault/VaultConfigurationProvider.cs:54 — 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.

C1 · Data Protection · No data-protection/encryption · ×1

No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.

D1 · Cyclomatic Complexity · CustomRollingFileAppender.InitializeFromOneFile (cyclomatic 17) · ×1

CustomRollingFileAppender.InitializeFromOneFile (cyclomatic 17) src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs:993 — CustomRollingFileAppender.InitializeFromOneFile 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.

D2 · Cognitive Complexity · CustomRollingFileAppender.RollOverRenameFiles (cognitive 43) · ×1

CustomRollingFileAppender.RollOverRenameFiles (cognitive 43) src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs:1538 — CustomRollingFileAppender.RollOverRenameFiles has cognitive complexity 43 (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. This file is where this pass's cognitive complexity CONCENTRATES: src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs holds 2 of the 8 methods over the threshold — including the worst — and 40 of the 56 points over it (71%), 4× the next-largest file (src/ViennaNET.Logging/Log4NetImpl/Log4NetConfigurationApplier.cs at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · CustomRollingFileAppender.InitializeFromOneFile (cognitive 27) · ×1

CustomRollingFileAppender.InitializeFromOneFile (cognitive 27) src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs:993 — CustomRollingFileAppender.InitializeFromOneFile has cognitive complexity 27 (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. This file is where this pass's cognitive complexity CONCENTRATES: src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs holds 2 of the 8 methods over the threshold — including the worst — and 40 of the 56 points over it (71%), 4× the next-largest file (src/ViennaNET.Logging/Log4NetImpl/Log4NetConfigurationApplier.cs at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · Log4NetConfigurationApplier.GetFileAppender (cognitive 25) · ×1

Log4NetConfigurationApplier.GetFileAppender (cognitive 25) src/ViennaNET.Logging/Log4NetImpl/Log4NetConfigurationApplier.cs:137 — Log4NetConfigurationApplier.GetFileAppender has cognitive complexity 25 (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 · ApplicationContextProvider.RegisterBoundedContexts (cognitive 17) · ×1

ApplicationContextProvider.RegisterBoundedContexts (cognitive 17) src/ViennaNET.Orm/Factories/ApplicationContextProvider.cs:65 — ApplicationContextProvider.RegisterBoundedContexts has cognitive complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · Validator.CheckDependsOnMembers (cognitive 16) · ×1

Validator.CheckDependsOnMembers (cognitive 16) src/ViennaNET.Validation/Validators/Validator.cs:129 — Validator.CheckDependsOnMembers has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ValidatorAsync.CheckDependsOnMembers (cognitive 16) · ×1

ValidatorAsync.CheckDependsOnMembers (cognitive 16) src/ViennaNET.Validation/Validators/ValidatorAsync.cs:108 — ValidatorAsync.CheckDependsOnMembers has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Code128.Encode (cognitive 16) · ×1

Code128.Encode (cognitive 16) src/ViennaNET.Word/Barcode/Code128.cs:202 — Code128.Encode has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · OpenXmlExcelProcessor.ProcessUrl (cognitive 16) · ×1

OpenXmlExcelProcessor.ProcessUrl (cognitive 16) src/ViennaNET.Excel/Impls/OpenXmlExcelProcessor.cs:115 — OpenXmlExcelProcessor.ProcessUrl 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.

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

REDACTED

D3 · God Classes · ClassTooLong · ×1

ClassTooLong: CustomRollingFileAppender src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.cs — ClassTooLong — 429 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 29 over it, 1.07× 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.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Duplicated block (103–105 lines × 2) · ×1

Duplicated block (103–105 lines × 2) src/ViennaNET.Redis/IRedisServer.cs:38 — src/ViennaNET.Redis/IRedisServer.cs:38-142 | src/ViennaNET.Redis/ISilentRedisServer.cs:38-140 — before extracting anything, compare `src/ViennaNET.Redis/IRedisServer.cs` and `src/ViennaNET.Redis/ISilentRedisServer.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

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

Duplicated block (31 lines × 2) src/ViennaNET.Redis/ICacheService.cs:9 — src/ViennaNET.Redis/ICacheService.cs:9-41 | src/ViennaNET.Redis/ISilentCacheService.cs:9-39 — before extracting anything, compare `src/ViennaNET.Redis/ICacheService.cs` and `src/ViennaNET.Redis/ISilentCacheService.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ViennaNET.Redis/ICacheService.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

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

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

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

Duplicated block (22 lines × 2) src/ViennaNET.Messaging.ActiveMQQueue/ActiveMqQueueConfiguration.cs:93 — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMqQueueConfiguration.cs:93-114 | src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueConfiguration.cs:116-137 — 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 (17 lines × 2) · ×1

Duplicated block (17 lines × 2) src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:334 — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:334-350 | src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:340-356 — before extracting anything, compare `src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs` and `src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:334` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

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

Duplicated block (15–16 lines × 2) src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:465 — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:465-480 | src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:475-489 — before extracting anything, compare `src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs` and `src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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.

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

Duplicated block (14–15 lines × 2) src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/PropertyRuleValidator.cs:44 — src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/PropertyRuleValidator.cs:44-58 | src/ViennaNET.Validation/Rules/FluentRule/RuleValidators/PropertyRuleValidatorAsync.cs:45-58 — 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 × 3) · ×1

Duplicated block (6 lines × 3) src/ViennaNET.Word/Document.cs:90 — src/ViennaNET.Word/Document.cs:90-95 | src/ViennaNET.Word/Document.cs:133-138 | src/ViennaNET.Word/Document.cs:177-182 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

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

Duplicated block (26 lines × 2) src/ViennaNET.Messaging/Context/MessagingCallContextAccessor.cs:11 — src/ViennaNET.Messaging/Context/MessagingCallContextAccessor.cs:11-39 | src/ViennaNET.WebApi.Configurators.CallContext/HttpCallContextAccessor.cs:11-36 — 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 (9 lines × 3) · ×1

Duplicated block (9 lines × 3) src/ViennaNET.Orm.DB2.Lnx/Db2SessionFactoryProviderGetter.cs:32 — src/ViennaNET.Orm.DB2.Lnx/Db2SessionFactoryProviderGetter.cs:32-40 | src/ViennaNET.Orm.DB2.Osx/Db2SessionFactoryProviderGetter.cs:32-40 | src/ViennaNET.Orm.DB2.Win/Db2SessionFactoryProviderGetter.cs:32-40 — `src/ViennaNET.Orm.DB2.Lnx/Db2SessionFactoryProviderGetter.cs` and `src/ViennaNET.Orm.DB2.Osx/Db2SessionFactoryProviderGetter.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 9 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

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

Duplicated block (21 lines × 2) src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:222 — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:222-242 | src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:209-229 — before extracting anything, compare `src/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs` and `src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 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 (6 lines × 2) · ×1

Duplicated block (6 lines × 2) src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:136 — src/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:136-141 | src/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:250-255 — 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.

D5 · Coupling · Unstable project ViennaNET.WebApi.Configurators.Security.Jwt · ×1

Unstable project ViennaNET.WebApi.Configurators.Security.Jwt src/ViennaNET.WebApi.Configurators.Security.Jwt/ViennaNET.WebApi.Configurators.Security.Jwt.csproj:1 — ViennaNET.WebApi.Configurators.Security.Jwt has instability 0.71 with 2 dependents.

D5 · Coupling · Unstable project ViennaNET.WebApi.Configurators.HttpClients.Ntlm · ×1

Unstable project ViennaNET.WebApi.Configurators.HttpClients.Ntlm src/ViennaNET.WebApi.Configurators.HttpClients.Ntlm/ViennaNET.WebApi.Configurators.HttpClients.Ntlm.csproj:1 — ViennaNET.WebApi.Configurators.HttpClients.Ntlm has instability 0.83 with 1 dependents.

D5 · Coupling · Unstable project ViennaNET.WebApi.Configurators.HttpClients.Jwt · ×1

Unstable project ViennaNET.WebApi.Configurators.HttpClients.Jwt src/ViennaNET.WebApi.Configurators.HttpClients.Jwt/ViennaNET.WebApi.Configurators.HttpClients.Jwt.csproj:1 — ViennaNET.WebApi.Configurators.HttpClients.Jwt has instability 0.83 with 1 dependents.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.

P12 · CI test-gate honesty · Coverage collected but not gated · ×1

Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.

P12 · CI test-gate honesty · Test suite runs only after the merge · ×1

Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.

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

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

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

Sync-over-async (deadlock risk) through `.Result` src/ViennaNET.Messaging/Sending/Impl/MessageSender.cs:77 — 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.

X27 · Collection changed while being enumerated · Collection is structurally changed while it is being enumerated · ×1

Collection is structurally changed while it is being enumerated src/ViennaNET.Logging/Log4NetImpl/Log4NetWrapper.cs:44 — `log4netWrapper._logs` is enumerated directly, and line 48 calls `log4netWrapper._logs.Add(…)` inside the loop body — a structural change to a `Dictionary`. The next `MoveNext` throws `InvalidOperationException: Collection was modified; enumeration operation may not execute`, so every pass that reaches this call ends the loop by exception instead of by running out of items, and the remaining items are never seen.

X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×1

Symbol treated as nullable, then dereferenced unguarded src/ViennaNET.WebApi/CompanyHostBuilderErrorHandler.cs:100 — This method contradicts itself about `exception`: line 91 writes `exception?.GetType`, which says `exception` can be null, but line 100 then dereferences it directly as `exception.Message` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `exception` truly cannot be null here, the `?.` is misleading. Settle it one way — test `exception` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.

Minor — 258 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×169

Orphaned file src/ViennaNET.Validation/Rules/FluentRule/CurrentValidatorHolderExtensions.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/ViennaNET.ArcSight/CefMessageSerializer.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/ViennaNET.Word/Document.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/ViennaNET.Utils/MayBeMonade.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/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.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/ViennaNET.Word/Barcode/Code128.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/ViennaNET.Validation/Rules/FluentRule/RuleValidationMemberBuilderExtensionsAsync.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/ViennaNET.Validation/Rules/FluentRule/RuleValidationMemberBuilderExtensions.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/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.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/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.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/ViennaNET.Utils/Annotations.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/ViennaNET.Extensions.Http/DependencyInjection/HttpClientServiceCollectionExtensions.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/ViennaNET.Logging/Logger.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/ViennaNET.Mediator/Mediators/Mediator.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/ViennaNET.Redis/Implementation/Silent/SilentRedisDatabase.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/ViennaNET.KasperskyScanEngine.Client/IKasperskyScanEngineApi.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/ViennaNET.Redis/IRedisServer.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/ViennaNET.Redis/ISilentRedisServer.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/ViennaNET.WebApi/CompanyHostBuilderActions.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/ViennaNET.WebApi.Abstractions/ICompanyHostBuilder.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/ViennaNET.Messaging/Processing/Impl/QueueReactorFactory.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/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.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/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.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/ViennaNET.EventSourcing/EventStore.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.
+ 144 more in this group — see findings.md.

D18 · Solution Shape · Thin analysable surface across projects · ×14

Thin analysable surface across projects: ViennaNET.Orm.DB2.Lnx.DefaultConfiguration src/ViennaNET.Orm.DB2.Lnx.DefaultConfiguration/ViennaNET.Orm.DB2.Lnx.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Orm.DB2.Lnx.DefaultConfiguration` has 13 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.07 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Orm.DB2.Win.DefaultConfiguration src/ViennaNET.Orm.DB2.Win.DefaultConfiguration/ViennaNET.Orm.DB2.Win.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Orm.DB2.Win.DefaultConfiguration` has 13 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.07 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Messaging.KafkaQueue.DefaultConfiguration src/ViennaNET.Messaging.KafkaQueue.DefaultConfiguration/ViennaNET.Messaging.KafkaQueue.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Messaging.KafkaQueue.DefaultConfiguration` has 13 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.07 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Orm.DB2.Osx.DefaultConfiguration src/ViennaNET.Orm.DB2.Osx.DefaultConfiguration/ViennaNET.Orm.DB2.Osx.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Orm.DB2.Osx.DefaultConfiguration` has 13 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.07 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Orm.MSSQL.DefaultConfiguration REDACTED — 14 project(s) carry only a thin slice of real code; `ViennaNET.Orm.MSSQL.DefaultConfiguration` has 14 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration src/ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration/ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration` has 14 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Orm.Oracle.DefaultConfiguration src/ViennaNET.Orm.Oracle.DefaultConfiguration/ViennaNET.Orm.Oracle.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Orm.Oracle.DefaultConfiguration` has 14 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.EventSourcing.DefaultConfiguration REDACTED — 14 project(s) carry only a thin slice of real code; `ViennaNET.EventSourcing.DefaultConfiguration` has 14 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Orm.PostgreSql.DefaultConfiguration src/ViennaNET.Orm.PostgreSql.DefaultConfiguration/ViennaNET.Orm.PostgreSql.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Orm.PostgreSql.DefaultConfiguration` has 14 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration src/ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration/ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration` has 15 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.Messaging.ActiveMQQueue.DefaultConfiguration src/ViennaNET.Messaging.ActiveMQQueue.DefaultConfiguration/ViennaNET.Messaging.ActiveMQQueue.DefaultConfiguration.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.Messaging.ActiveMQQueue.DefaultConfiguration` has 17 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.WebApi.WindowsHosting src/ViennaNET.WebApi.WindowsHosting/ViennaNET.WebApi.WindowsHosting.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.WebApi.WindowsHosting` has 21 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.05 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.WebApi.Runners.BaseKestrel src/ViennaNET.WebApi.Runners.BaseKestrel/ViennaNET.WebApi.Runners.BaseKestrel.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.WebApi.Runners.BaseKestrel` has 27 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.04 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ViennaNET.WebApi.Runners.BaseHttpSys src/ViennaNET.WebApi.Runners.BaseHttpSys/ViennaNET.WebApi.Runners.BaseHttpSys.csproj — 14 project(s) carry only a thin slice of real code; `ViennaNET.WebApi.Runners.BaseHttpSys` has 27 significant line(s). The mean analysable-surface weight is 89 %; this project lowers Solution Shape by about 0.04 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.

D10 · Test Quality · Mock-dominated test · ×13

Mock-dominated test: Send_CorrectSettingsAndMessage_MessageCorrectlySent tests/ViennaNET.ArcSight.Tests/Unit/ArcSightClientTests.cs:49 — This test sets up 4 test doubles (for example `new Mock<IErrorHandlingPoliciesFactory>()`) against 3 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: GetScopedSession_CreateRepository_SessionManagerGotFromScope tests/ViennaNET.Orm.Tests/Unit/Factories/EntityFactoryServiceTests.cs:174 — This test sets up 4 test doubles (for example `new Mock<ISessionManagerProvider>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: RollbackAll_HasNoSessions_NothingCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:239 — This test sets up 3 test doubles (for example `new Mock<ITransaction>()`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: RollbackAll_TransactionIsActive_RollbackCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:259 — This test sets up 3 test doubles (for example `new Mock<ITransaction>()`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: RollbackAll_TransactionIsInactive_RollbackDidNotCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:280 — This test sets up 3 test doubles (for example `new Mock<ITransaction>()`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: RollbackAll_CloseSessionsAndHasException_SessionClearCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:301 — This test sets up 3 test doubles (for example `new Mock<ITransaction>()`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: RollbackAllAsync_TransactionIsActive_RollbackCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:327 — This test sets up 3 test doubles (for example `new Mock<ITransaction>()`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: RollbackAllAsync_TransactionIsInactive_RollbackDidNotCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:348 — This test sets up 3 test doubles (for example `new Mock<ITransaction>()`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: RollbackAllAsync_CloseSessionsAndHasException_SessionClearCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:369 — This test sets up 3 test doubles (for example `new Mock<ITransaction>()`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: GetStatelessSession_SimpleCall_SessionMethodCalled tests/ViennaNET.Orm.Tests/Unit/Factories/ScopedSessionManagerTests.cs:395 — This test sets up 4 test doubles (for example `new Mock<IStatelessSession>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: MarkDirty_CallsSessionProvider_EvictMethodCalled tests/ViennaNET.Orm.Tests/Unit/Repositories/UnitOfWorkTests.cs:104 — This test sets up 3 test doubles (for example `new Mock<ISessionManager>()`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: MarkDirtyAsync_CallsSessionProvider_EvictMethodCalled tests/ViennaNET.Orm.Tests/Unit/Repositories/UnitOfWorkTests.cs:141 — This test sets up 3 test doubles (for example `new Mock<ISessionManager>()`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: AppendToStreamWithReplyNotSendableEventAndAsResultWasNotSendToQueue tests/ViennaNET.EventSourcing.Tests/EventStoreTests.cs:181 — This test sets up 3 test doubles (for example `new Mock<ISerializedMessageRpcSender<string, string>>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.

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

Interpolated log message defeats structured logging src/ViennaNET.Logging/LogAutoStopWatch.cs:37 — 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/ViennaNET.Mediator/Collectors/EventCollector.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/ViennaNET.Mediator/Collectors/EventCollector.cs:119 — 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/ViennaNET.ArcSight/ErrorHandlingPolicyFactory.cs:34 — 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/ViennaNET.Redis/Diagnostic/RedisConnectionChecker.cs:66 — 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/ViennaNET.Security.Jwt/Impl/JwtTokenReader.cs:38 — 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/ViennaNET.Messaging/Processing/Impl/Subscribe/QueueSubscribedReactorBase.cs:276 — 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/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapter.cs:507 — 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/ViennaNET.Messaging.RabbitMQQueue/RabbitMQQueueMessageAdapter.cs:458 — 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/ViennaNET.WebApi.Configurators.Common/Middleware/SetLoggingScopeMiddleware.cs:50 — 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/ViennaNET.Messaging.KafkaQueue/KafkaQueueMessageAdapter.cs:269 — 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/ViennaNET.Messaging.ActiveMQQueue/ActiveMQQueueMessageAdapter.cs:503 — 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.

X10 · Duplicated predicate · Duplicated predicate · ×7

Duplicated predicate src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueConfiguration.cs:133 — `TransactionEnabled && ProcessingType != MessageProcessingType.ThreadStrategy` appears character-identically in 2 files — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMqQueueConfiguration.cs, src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueConfiguration.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/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs:201 — `_serviceHealthDependent && _hasDiagnosticErrors` appears character-identically in 2 files — src/ViennaNET.Messaging/Processing/Impl/Poll/QueuePollingReactorBase.cs, src/ViennaNET.Messaging/Processing/Impl/Subscribe/QueueSubscribedReactorBase.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/ViennaNET.WebApi.Configurators.HttpSys/HttpSysConfigurator.cs:86 — `hostConfiguration.UseHsts == true && !env.IsDevelopment()` appears character-identically in 2 files — src/ViennaNET.WebApi.Configurators.HttpSys/HttpSysConfigurator.cs, src/ViennaNET.WebApi.Configurators.Kestrel/KestrelConfigurator.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/ViennaNET.WebApi.Configurators.HttpSys/HttpSysConfigurator.cs:91 — `hostConfiguration.UseStrictHttps.HasValue && hostConfiguration.UseStrictHttps.Value` appears character-identically in 2 files — src/ViennaNET.WebApi.Configurators.HttpSys/HttpSysConfigurator.cs, src/ViennaNET.WebApi.Configurators.Kestrel/KestrelConfigurator.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/ViennaNET.Orm/Factories/SessionFactoryProvider.cs:101 — `i.IsGenericType && i.GetGenericTypeDefinition() == typeof(IEntityKey<>)` appears character-identically in 2 files — src/ViennaNET.Orm.Seedwork/BoundedContext.cs, src/ViennaNET.Orm/Factories/SessionFactoryProvider.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/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapterConstructor.cs:38 — `queueConfiguration.ProcessingType == MessageProcessingType.Subscribe || queueConfiguration.ProcessingType == MessageProcessingType.Subscribe…` appears character-identically in 2 files — src/ViennaNET.Messaging.ActiveMQQueue/ActiveMqQueueMessageAdapterConstructor.cs, src/ViennaNET.Messaging.MQSeriesQueue/MqSeriesQueueMessageAdapterConstructor.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/ViennaNET.Diagnostic/HealthCheckingService.cs:36 — `x.Status != DiagnosticStatus.Ok && !x.IsSkipResult` appears character-identically in 2 files — src/ViennaNET.Diagnostic/HealthCheckingService.cs, REDACTED. 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 · ×5

Fat interface: IRedisDatabase (48 members) src/ViennaNET.Redis/IRedisDatabase.cs:12 — `IRedisDatabase` declares 48 members: `ObjectGet`, `ObjectGet`, `HashObjectGet`, `HashObjectGet`, `HashObjectGetAll`, `ObjectSet`, `ObjectSet`, `ObjectSet`, `HashObjectSet`, `HashObjectSet`, `ObjectGetAsync`, `ObjectGetAsync`, `HashObjectGetAsync`, `HashObjectGetAsync`, `HashObjectGetAllAsync`, `ObjectSetAsync`, `ObjectSetAsync`, `ObjectSetAsync`, `HashObjectSetAsync`, `HashObjectSetAsync`, `StringGet`, `StringGet`, `HashStringGet`, `HashStringGet`, `HashStringGetAll`, `StringSet`, `StringSet`, `StringSet`, `HashStringSet`, `HashStringSet`, `StringGetAsync`, `StringGetAsync`, `HashStringGetAsync`, `HashStringGetAsync`, `HashStringGetAllAsync`, `StringSetAsync`, `StringSetAsync`, `StringSetAsync`, `HashStringSetAsync`, `HashStringSetAsync`, and 8 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 48 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 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: IRedisServer (22 members) src/ViennaNET.Redis/IRedisServer.cs:13 — `IRedisServer` declares 22 members: `IsConnected`, `EndPoint`, `ServerType`, `Version`, `IsSlave`, `Keys`, `Save`, `SaveAsync`, `ConfigGet`, `ConfigGetAsync`, `ConfigSet`, `ConfigSetAsync`, `Info`, `InfoAsync`, `LastSave`, `LastSaveAsync`, `Time`, `TimeAsync`, `FlushAllDatabases`, `FlushAllDatabasesAsync`, `FlushDatabase`, `FlushDatabaseAsync`. 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: ISilentRedisServer (22 members) src/ViennaNET.Redis/ISilentRedisServer.cs:13 — `ISilentRedisServer` declares 22 members: `IsConnected`, `EndPoint`, `ServerType`, `Version`, `IsSlave`, `Keys`, `Save`, `SaveAsync`, `ConfigGet`, `ConfigGetAsync`, `ConfigSet`, `ConfigSetAsync`, `Info`, `InfoAsync`, `LastSave`, `LastSaveAsync`, `Time`, `TimeAsync`, `FlushAllDatabases`, `FlushAllDatabasesAsync`, `FlushDatabase`, `FlushDatabaseAsync`. 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: IWorkSheet (20 members) src/ViennaNET.Excel/Contracts/IWorkSheet.cs:5 — `IWorkSheet` declares 20 members: `Name`, `this[]`, `Visible`, `Rows`, `HideColumn`, `ShowColumn`, `ColumnHidden`, `GetColumnWidth`, `CopyStyles`, `SetColumnWidth`, `ShiftDownRow`, `RecalculateFormulas`, `HideRow`, `ReadCellByName`, `CreateVerticalRange`, `CreateRange`, `CreateHierarchicalRange`, `MergeCells`, `CreateStyle`, `CreateStyle`. 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 20 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 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: ICompanyHostBuilder (25 members) src/ViennaNET.WebApi.Abstractions/ICompanyHostBuilder.cs:13 — `ICompanyHostBuilder` declares 25 members: `BuildWebHost`, `AddMvcBuilderConfiguration`, `AddMvcOptionsConfiguration`, `ConfigureApp`, `AddMiddleware`, `ConfigureContainer`, `ConfigureContainer`, `InitializeContainer`, `RegisterServices`, `RegisterServices`, `CreateContainer`, `VerifyContainer`, `UseServer`, `AddOnStartAction`, `AddOnStartAction`, `AddOnStoppingAction`, `AddOnStoppingAction`, `AddOnStoppedAction`, `AddOnStoppedAction`, `AddExceptionHandler`, `AddExceptionHandler`, `AddExceptionHandler`, `AddExceptionHandler`, `RegisterHostBuilderAction`, `RegisterConfigurationBuilderAction`. 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 25 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.

D12 · Dependency Hygiene · Outdated · ×5

Outdated: coverlet.msbuild tests/Directory.Build.props:26 — coverlet.msbuild 6.0.2 → 10.1.0 available (referenced by ViennaNET.Redis.Tests).
Outdated: NunitXml.TestLogger tests/Directory.Build.props:23 — NunitXml.TestLogger 3.1.20 → 8.0.0 available (referenced by ViennaNET.Redis.Tests).
Outdated: Oracle.ManagedDataAccess.Core src/ViennaNET.Orm.Oracle/ViennaNET.Orm.Oracle.csproj:7 — Oracle.ManagedDataAccess.Core 3.21.120 → 23.26.400 available (referenced by ViennaNET.Orm.Oracle).
Outdated: Swashbuckle.AspNetCore src/ViennaNET.WebApi.Configurators.Swagger.UiJwtAuth/ViennaNET.WebApi.Configurators.Swagger.UiJwtAuth.csproj:18 — Swashbuckle.AspNetCore 6.5.0 → 10.3.1 available (referenced by ViennaNET.WebApi.Configurators.Swagger).
Outdated: KubernetesClient REDACTED:16 — REDACTED → 21.0.8 available (referenced by ViennaNET.Extensions.Configuration.Kubernetes).

M4 · Documentation accuracy · README/code drift · ×4

README/code drift README.md:4 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
README/code drift src/ViennaNET.Extensions.Configuration.HashicorpVault/README.md:23 — src/ViennaNET.Extensions.Configuration.HashicorpVault/README.md installs the package `ViennaNET.Extensions.Configuration.HashicorpVault` (`dotnet add package ViennaNET.Extensions.Configuration.HashicorpVault`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/ViennaNET.Extensions.Http/README.md:31 — src/ViennaNET.Extensions.Http/README.md installs the package `ViennaNET.Extensions.Http` (`dotnet add package ViennaNET.Extensions.Http`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift src/ViennaNET.KasperskyScanEngine.Client/README.md:25 — src/ViennaNET.KasperskyScanEngine.Client/README.md installs the package `ViennaNET.KasperskyScanEngine.Client` (`dotnet add package ViennaNET.KasperskyScanEngine.Client`), but no project or props file references it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

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

Most significant orphaned file src/ViennaNET.Logging/Log4NetImpl/CustomRollingFileAppender.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/ViennaNET.Redis/IRedisDatabase.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/ViennaNET.Redis/Implementation/Default/RedisDatabase.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.

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

Commented-out code src/ViennaNET.Excel/Impls/NPoiExcelFile.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/ViennaNET.Logging/Log4NetImpl/Log4NetConfigurationApplier.cs:168 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).

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 src/ViennaNET.WebApi/CompanyHostBuilder.cs:68 — 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.

C2 · Access Controls · Thin authorization enforcement · ×1

Thin authorization enforcement — Authorization machinery exists but no [Authorize] usage and no imperative guard calls were found at handlers.

C4 · Data Retention · Partial data-retention evidence · ×1

Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob), a documented retention period / data-expiry.

D19 · Documentation Quality · Documentation · ×1

Documentation: no usage examples src/ViennaNET.Messaging.MQSeriesQueue/README.md — The README describes MqSeriesQueueConfiguration and its queues fields but does not show how to run the assembly or where to find the queueString field described in detail. Add a short runnable example showing how to configure and start an MQSeries queue, and point readers to the configuration file's queueString section.

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/`.

D27 · Navigability · Pass-through layer · ×1

Pass-through layer src/ViennaNET.Validation/Validators/RulesValidatorAsync.cs:10 — RulesValidatorAsync: all 4 public methods forward their arguments unchanged to validator and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call validator directly, or give the layer a job.

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

REDACTED

D34 · Knowledge Freshness · Dormant codebase · ×1

Dormant codebase — 172 of 172 significant files have no living knowledge — the codebase as a whole is dormant, not 172 separate risks. Counted over 172 of the 613 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.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D39 · IL Efficiency · IL efficiency · ×1

IL efficiency: 2 authored method(s) exceed the IL budget src/ViennaNET.ArcSight/Validation/ExtensionsRule.cs:7 — 2 of 2157 first-party methods compile to oversized IL bodies (> 250 instructions); worst: ViennaNET.ArcSight.Validation.ExtensionsRule..ctor @ src/ViennaNET.ArcSight/Validation/ExtensionsRule.cs:7, 2139 IL instructions; that pulled this dimension to 10.0/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.

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.

P12 · CI test-gate honesty · Sleep-based test synchronization · ×1

Sleep-based test synchronization — 6 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.

P2 · Observability · Logging is not universal · ×1

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

P4 · Deployment & Rollback · No release approval gate · ×1

No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

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

Not all async methods take a CancellationToken — Only 37/102 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 · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1

Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.1 `!` suppressions per 1k syntax nodes — 9 suppression(s) across the 126529 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 on parse failure · ×1

Silent fallback default on parse failure src/ViennaNET.Orm/Conventions/IntToString.cs:35 — `NullSafeGet` falls back to `0` when `int.TryParse(value.ToString(), out var unsusedVal)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.

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

Silent fallback default in catch src/ViennaNET.Excel/Impls/NPoiWorkSheet.cs:62 — `ColumnHidden` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.

Minor — 131 finding(s)

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

XML-doc coverage: ViennaNET.WebApi src/ViennaNET.WebApi/ViennaNET.WebApi.csproj — ViennaNET.WebApi: 57 % XML-doc coverage (32/56).
XML-doc coverage: ViennaNET.Security src/ViennaNET.Security/ViennaNET.Security.csproj — ViennaNET.Security: 100 % XML-doc coverage (2/2).
XML-doc coverage: ViennaNET.Utils src/ViennaNET.Utils/ViennaNET.Utils.csproj — ViennaNET.Utils: 69 % XML-doc coverage (76/110).
XML-doc coverage: ViennaNET.HttpClient src/ViennaNET.HttpClient/ViennaNET.HttpClient.csproj — ViennaNET.HttpClient: 91 % XML-doc coverage (10/11).
XML-doc coverage: ViennaNET.Logging REDACTED — ViennaNET.Logging: 58 % XML-doc coverage (94/163).
XML-doc coverage: ViennaNET.Orm src/ViennaNET.Orm/ViennaNET.Orm.csproj — ViennaNET.Orm: 56 % XML-doc coverage (113/200).
XML-doc coverage: ViennaNET.Orm.Seedwork src/ViennaNET.Orm.Seedwork/ViennaNET.Orm.Seedwork.csproj — ViennaNET.Orm.Seedwork: 67 % XML-doc coverage (12/18).
XML-doc coverage: ViennaNET.Orm.DefaultConfiguration src/ViennaNET.Orm.DefaultConfiguration/ViennaNET.Orm.DefaultConfiguration.csproj — ViennaNET.Orm.DefaultConfiguration: 50 % XML-doc coverage (2/4).
XML-doc coverage: ViennaNET.Mediator.DefaultConfiguration src/ViennaNET.Mediator.DefaultConfiguration/ViennaNET.Mediator.DefaultConfiguration.csproj — ViennaNET.Mediator.DefaultConfiguration: 67 % XML-doc coverage (10/15).
XML-doc coverage: ViennaNET.Mediator.Seedwork src/ViennaNET.Mediator.Seedwork/ViennaNET.Mediator.Seedwork.csproj — ViennaNET.Mediator.Seedwork: 100 % XML-doc coverage (5/5).
XML-doc coverage: ViennaNET.Mediator src/ViennaNET.Mediator/ViennaNET.Mediator.csproj — ViennaNET.Mediator: 69 % XML-doc coverage (35/51).
XML-doc coverage: ViennaNET.Orm.MSSQL.DefaultConfiguration REDACTED — ViennaNET.Orm.MSSQL.DefaultConfiguration: 100 % XML-doc coverage (2/2).
XML-doc coverage: ViennaNET.ArcSight src/ViennaNET.ArcSight/ViennaNET.ArcSight.csproj — ViennaNET.ArcSight: 17 % XML-doc coverage (32/191).
XML-doc coverage: ViennaNET.Redis src/ViennaNET.Redis/ViennaNET.Redis.csproj — ViennaNET.Redis: 20 % XML-doc coverage (41/207).
XML-doc coverage: ViennaNET.Redis.DefaultConfiguration src/ViennaNET.Redis.DefaultConfiguration/ViennaNET.Redis.DefaultConfiguration.csproj — ViennaNET.Redis.DefaultConfiguration: 100 % XML-doc coverage (2/2).
XML-doc coverage: ViennaNET.Validation src/ViennaNET.Validation/ViennaNET.Validation.csproj — ViennaNET.Validation: 69 % XML-doc coverage (204/294).
XML-doc coverage: ViennaNET.ArcSight.DefaultConfiguration REDACTED — ViennaNET.ArcSight.DefaultConfiguration: 100 % XML-doc coverage (2/2).
XML-doc coverage: ViennaNET.Specifications src/ViennaNET.Specifications/ViennaNET.Specifications.csproj — ViennaNET.Specifications: 100 % XML-doc coverage (15/15).
XML-doc coverage: ViennaNET.Security.Jwt src/ViennaNET.Security.Jwt/ViennaNET.Security.Jwt.csproj — ViennaNET.Security.Jwt: 28 % XML-doc coverage (7/25).
XML-doc coverage: ViennaNET.Diagnostic src/ViennaNET.Diagnostic/ViennaNET.Diagnostic.csproj — ViennaNET.Diagnostic: 69 % XML-doc coverage (20/29).
XML-doc coverage: ViennaNET.Messaging REDACTED — ViennaNET.Messaging: 91 % XML-doc coverage (202/221).
XML-doc coverage: ViennaNET.Messaging.MQSeriesQueue src/ViennaNET.Messaging.MQSeriesQueue/ViennaNET.Messaging.MQSeriesQueue.csproj — ViennaNET.Messaging.MQSeriesQueue: 93 % XML-doc coverage (38/41).
XML-doc coverage: ViennaNET.Messaging.RabbitMQQueue src/ViennaNET.Messaging.RabbitMQQueue/ViennaNET.Messaging.RabbitMQQueue.csproj — ViennaNET.Messaging.RabbitMQQueue: 89 % XML-doc coverage (32/36).
XML-doc coverage: ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration src/ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration/ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration.csproj — ViennaNET.Messaging.RabbitMQQueue.DefaultConfiguration: 100 % XML-doc coverage (2/2).
XML-doc coverage: ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration src/ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration/ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration.csproj — ViennaNET.Messaging.MQSeriesQueue.DefaultConfiguration: 100 % XML-doc coverage (2/2).
+ 59 more in this group — see findings.md.

D12 · Dependency Hygiene · Outdated · ×47

Outdated: Newtonsoft.Json — Newtonsoft.Json 13.0.3 → 13.0.4 available (referenced by ViennaNET.WebApi).
Outdated: Microsoft.Extensions.Http.Polly — Microsoft.Extensions.Http.Polly 8.0.4 → 10.0.13 available (referenced by ViennaNET.HttpClient).
Outdated: Polly — Polly 8.2.0 → 8.8.0 available (referenced by ViennaNET.HttpClient).
Outdated: log4net — REDACTED → 3.5.0 available (referenced by ViennaNET.Logging).
Outdated: Microsoft.Extensions.Configuration.Binder — Microsoft.Extensions.Configuration.Binder 8.0.1 → 10.0.13 available (referenced by ViennaNET.Logging).
Outdated: Microsoft.Extensions.Configuration.Json — Microsoft.Extensions.Configuration.Json 8.0.0 → 10.0.13 available (referenced by ViennaNET.Logging).
Outdated: Microsoft.Extensions.Logging.Abstractions — Microsoft.Extensions.Logging.Abstractions 8.0.1 → 10.0.13 available (referenced by ViennaNET.Logging).
Outdated: FluentNHibernate — FluentNHibernate 3.3.0 → 3.5.0 available (referenced by ViennaNET.Orm).
Outdated: NHibernate — REDACTED → 5.7.0 available (referenced by ViennaNET.Orm).
Outdated: SimpleInjector.Packaging — SimpleInjector.Packaging 5.0.0 → 5.5.0 available (referenced by ViennaNET.Orm.DefaultConfiguration).
Outdated: Microsoft.Extensions.Options.ConfigurationExtensions — Microsoft.Extensions.Options.ConfigurationExtensions 8.0.0 → 10.0.13 available (referenced by ViennaNET.Redis).
Outdated: StackExchange.Redis — StackExchange.Redis 2.7.33 → 3.4.5 available (referenced by ViennaNET.Redis).
Outdated: Microsoft.IdentityModel.Tokens — Microsoft.IdentityModel.Tokens 7.5.1 → 8.23.0 available (referenced by ViennaNET.Security.Jwt).
Outdated: System.IdentityModel.Tokens.Jwt — System.IdentityModel.Tokens.Jwt 7.5.1 → 8.23.0 available (referenced by ViennaNET.Security.Jwt).
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.9.0 → 18.11.0 available (referenced by ViennaNET.Redis.Tests).
Outdated: Moq — Moq 4.20.70 → 4.21.0 available (referenced by ViennaNET.Redis.Tests).
Outdated: NUnit — NUnit 4.1.0 → 5.0.0 available (referenced by ViennaNET.Redis.Tests).
Outdated: NUnit.Analyzers — NUnit.Analyzers 4.1.0 → 4.15.0 available (referenced by ViennaNET.Redis.Tests).
Outdated: NUnit3TestAdapter — NUnit3TestAdapter 4.5.0 → 6.3.1 available (referenced by ViennaNET.Redis.Tests).
Outdated: Microsoft.Bcl.AsyncInterfaces — Microsoft.Bcl.AsyncInterfaces 8.0.0 → 10.0.13 available (referenced by ViennaNET.Mediator.Tests).
Outdated: Microsoft.Extensions.Configuration — Microsoft.Extensions.Configuration 8.0.0 → 10.0.13 available (referenced by ViennaNET.ArcSight.Tests).
Outdated: Microsoft.Extensions.Logging — Microsoft.Extensions.Logging 8.0.0 → 10.0.13 available (referenced by ViennaNET.Orm.Tests).
Outdated: Microsoft.Extensions.Logging.Console — Microsoft.Extensions.Logging.Console 8.0.0 → 10.0.13 available (referenced by ViennaNET.Orm.Tests).
Outdated: System.Text.Json — REDACTED → 10.0.13 available (referenced by ViennaNET.Messaging).
Outdated: IBMXMSDotnetClient — IBMXMSDotnetClient 9.3.4.1 → 10.0.1 available (referenced by ViennaNET.Messaging.MQSeriesQueue).
+ 22 more in this group — see findings.md.

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-eeaa5c24e3b84d65b8d77edcf0cf8273/history.json --exit-code 0 --source .	2	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-eeaa5c24e3b84d65b8d77edcf0cf8273/tree.json --exit-code 0 --source .	2	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 .	23	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list ViennaNET.sln package --vulnerable --include-transitive --format json	25	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.	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 01a16132-469b-7085-a16c-ba42609212fb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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 · 71% · Strong ·

At a glance — Architecture · 91% · Exemplary ·

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

At a glance — Readiness · 42% · Weak · gated by D12, P7 ·

At a glance — Security · 44% · Weak · gated by D29, D30, D36, C1, C2 ·

At a glance — Performance · 60% · 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

Downloadable artifacts