yongpengW/NexusStack

Executive summary

yongpengW/NexusStack scores 38 out of 100, which would normally be rated Adequate, but it is rated Weak because its weakest group of dimensions, Testing, is rated Critical. The standard never rates a score more than one step above its weakest group, so a high average can't hide a weak area. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 29 and is rated Weak. Its Test Distribution dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 No tests found finding(s) in Test Distribution and to resolve the 10 Leaked secret finding(s) in REDACTED Scanning, and if Production Readiness rose to 70, the score would rise from 38 to about 46.

45 findings are critical: 12 in Explicit Debt, 12 in Secrets (history), ten in REDACTED Scanning, four in Dependency Vulnerabilities, four in IaC & Container Security, two in Web-Security Posture and one in Coupling.

Watchdog couldn't measure Dependency Hygiene, Documentation Quality and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 20,890 lines, which would take an estimated 0.3 person-years, around €51,000, to rebuild.

Code Health 52 Adequate, capped by Structured logging Architecture 78 Strong Maturity 34 Adequate, capped by Architecture documentation and Documentation accuracy Production Readiness 29 Weak, capped by Test Distribution, REDACTED Scanning, Outbound HTTP resilience and Library API & versioning Security and Compliance 60 Adequate, capped by Secrets (history) and Web-Security Posture Event-Driven 54 Adequate Performance 60 Strong

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 29 · counts for 46%Maturity 34 · counts for 25%Code Health 52 · counts for 14%Event-Driven 54 · counts for 8%Security and Compliance 60 · counts for 4%Performance 60 · counts for 2%Architecture 78 · counts for 1%

If Production Readiness rose from 29 to 70, the lowest score rated Strong, the score would rise from 38 to about 46.

Code composition: what the lines of code are

Business logic 33%Supporting code 52%Generated by tools 16%

New since the last survey: 155 findings

These 155 critical or serious findings weren't in the previous survey, on 7 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
Explicit Debt · Dead code: FormAsync Infrastructure/Client/HttpClientService.cs
Explicit Debt · Dead code: PostFormUrlEncodedAsync Infrastructure/Client/HttpClientService.cs
Explicit Debt · Dead code: PostDingtalkMsgAsync Infrastructure/Client/HttpClientService.cs
Explicit Debt · Dead code: PostQyWinXinMsgAsync Infrastructure/Client/HttpClientService.cs
Explicit Debt · Dead code: PostRequest Infrastructure/Client/RequestModel.cs
Explicit Debt · Dead code: XmlConverter Infrastructure/Converters/XmlConverter.cs
Explicit Debt · Dead code: GetDownloadCenterUri Infrastructure/FileStroage/IFileStorage.cs
Explicit Debt · Dead code: GetFile Infrastructure/FileStroage/IFileStorage.cs
Explicit Debt · Dead code: GetConfigFile Infrastructure/FileStroage/IFileStorage.cs
Explicit Debt · Dead code: UploadConfigAsync Infrastructure/FileStroage/IFileStorage.cs
Explicit Debt · Dead code: GeneratePresignedConfigUri Infrastructure/FileStroage/IFileStorage.cs
Explicit Debt · Dead code: SignalROptions Infrastructure/Options/SignalROptions.cs
Explicit Debt · Dead code: GetRedisKeys Infrastructure/Utils/CollectExtensions.cs
Explicit Debt · Dead code: ConvertExpandoObject Infrastructure/Utils/CollectExtensions.cs
Explicit Debt · Dead code: RebuilderMetaDataQueryParemeter Infrastructure/Utils/CollectExtensions.cs
Explicit Debt · Dead code: CheckIdColumnAndAddRow Infrastructure/Utils/CollectExtensions.cs
Explicit Debt · Dead code: ObjectToMap Infrastructure/Utils/ConvertHelper.cs
Explicit Debt · Dead code: GetDocPathByFileName Infrastructure/Utils/DocsHelper.cs
Explicit Debt · Dead code: GetMD5 Infrastructure/Utils/EncryptionHelp.cs
Explicit Debt · Dead code: RsaEncrypt Infrastructure/Utils/EncryptionHelp.cs
Explicit Debt · Dead code: GenerateBatchNumber Infrastructure/Utils/EncryptionHelp.cs
Explicit Debt · Dead code: GenerateCainiaoSha256Signature Infrastructure/Utils/EncryptionHelp.cs
Explicit Debt · Dead code: FileHelper Infrastructure/Utils/FileHelper.cs
Explicit Debt · Dead code: ToRoundUp Infrastructure/Utils/MoneyExtensions.cs
Explicit Debt · Dead code: ToRoundDown Infrastructure/Utils/MoneyExtensions.cs
Explicit Debt · Dead code: IsNull Infrastructure/Utils/ObjectExtensions.cs
Explicit Debt · Dead code: Long Infrastructure/Utils/StringExtensions.cs
Explicit Debt · Dead code: toBigIntList Infrastructure/Utils/StringExtensions.cs
Explicit Debt · Dead code: ToMaskSensitiveInfo Infrastructure/Utils/StringExtensions.cs
Explicit Debt · Dead code: ToShopIdString Infrastructure/Utils/StringExtensions.cs
Explicit Debt · Dead code: ToShopIdString Infrastructure/Utils/StringExtensions.cs
Explicit Debt · Dead code: ToShopIdArray Infrastructure/Utils/StringExtensions.cs
Explicit Debt · Dead code: SnapshotAsync Infrastructure/Video/VideoHelper.cs
Explicit Debt · Dead code: TranscodeAsync Infrastructure/Video/VideoHelper.cs
Explicit Debt · Dead code: DashboardChartDataDto Domain/NexusStack.Core/Dtos/Dashboard/DashboardChartDataDto.cs
Explicit Debt · Dead code: DashboardChartDataQueryDto Domain/NexusStack.Core/Dtos/Dashboard/DashboardChartDataQueryDto.cs
Explicit Debt · Dead code: DashboardHotSalesDto Domain/NexusStack.Core/Dtos/Dashboard/DashboardHotSalesDto.cs
Explicit Debt · Dead code: DashboardOverviewDto Domain/NexusStack.Core/Dtos/Dashboard/DashboardOverviewDto.cs
Explicit Debt · Dead code: ExportExcelRequestDto Domain/NexusStack.Core/Dtos/DownloadCenter/ExportExcelRequestDto.cs
Explicit Debt · Dead code: IdDropDownDto Domain/NexusStack.Core/Dtos/DropDownDto.cs
Explicit Debt · Dead code: ValueDropDownDto Domain/NexusStack.Core/Dtos/DropDownDto.cs
Explicit Debt · Dead code: FileQueryDto Domain/NexusStack.Core/Dtos/Files/FileQueryDto.cs
Explicit Debt · Dead code: KeyValueDto Domain/NexusStack.Core/Dtos/KeyValueDto.cs
Explicit Debt · Dead code: DecimalKeyValueDto Domain/NexusStack.Core/Dtos/KeyValueDto.cs
Explicit Debt · Dead code: IntKeyValueDto Domain/NexusStack.Core/Dtos/KeyValueDto.cs
Explicit Debt · Dead code: OpenApiBaseRequestDto Domain/NexusStack.Core/Dtos/OpenApiBaseRequestDto.cs
Explicit Debt · Dead code: AppConfigDto Domain/NexusStack.Core/Dtos/OpenAppConfigs/AppConfigDto.cs
Explicit Debt · Dead code: Clone Domain/NexusStack.Core/Dtos/Regions/RegionExportDto.cs
Explicit Debt · Dead code: RegionExportQueryDto Domain/NexusStack.Core/Dtos/Regions/RegionExportQueryDto.cs
Explicit Debt · Dead code: GetData Domain/NexusStack.Core/Entities/AsyncTasks/AsyncTaskExtensions.cs
Explicit Debt · Dead code: UpdateClaimsFromDictionary Domain/NexusStack.Core/Extensions/ClaimsIdentityExtensions.cs
Explicit Debt · Dead code: CreateDelayedTaskAsync Domain/NexusStack.Core/Services/Interfaces/IAsyncTaskService.cs
Explicit Debt · Dead code: ExportExcelAsync Domain/NexusStack.Core/Services/Interfaces/IDownloadService.cs
Explicit Debt · Dead code: GetFileByUrlAsync Domain/NexusStack.Core/Services/Interfaces/IFileService.cs
Explicit Debt · Dead code: GetFilesByIds Domain/NexusStack.Core/Services/Interfaces/IFileService.cs
Explicit Debt · Dead code: UploadFromUrlAsync Domain/NexusStack.Core/Services/Interfaces/IFileService.cs
Explicit Debt · Dead code: GetExportFiles Domain/NexusStack.Core/Services/Interfaces/IFileService.cs
Explicit Debt · Dead code: NotifyToUserAsync Domain/NexusStack.Core/Services/Interfaces/INotificationRelayService.cs
Explicit Debt · Dead code: NotifyToGroupAsync Domain/NexusStack.Core/Services/Interfaces/INotificationRelayService.cs
Explicit Debt · Dead code: NotifyToAllAsync Domain/NexusStack.Core/Services/Interfaces/INotificationRelayService.cs
Explicit Debt · Dead code: SystemLogAsync Domain/NexusStack.Core/Services/Interfaces/IOperationLogService.cs
Explicit Debt · Dead code: RequestLogAsync Domain/NexusStack.Core/Services/Interfaces/IOperationLogService.cs
Explicit Debt · Dead code: ExceptionLogAsync Domain/NexusStack.Core/Services/Interfaces/IOperationLogService.cs
Explicit Debt · Dead code: JudgeHasPermissionAsync Domain/NexusStack.Core/Services/Interfaces/IPermissionService.cs
Explicit Debt · Dead code: CheckUserRoleExists Domain/NexusStack.Core/Services/Interfaces/IUserRoleService.cs
Explicit Debt · Dead code: CheckCurrentExists Domain/NexusStack.Core/Services/Interfaces/IUserService.cs
Explicit Debt · Dead code: CheckUserExists Domain/NexusStack.Core/Services/Interfaces/IUserService.cs
Explicit Debt · Dead code: GenerateCaptchaAsync Domain/NexusStack.Core/Services/Interfaces/IUserTokenService.cs
Explicit Debt · Dead code: ValidateCaptchaAsync Domain/NexusStack.Core/Services/Interfaces/IUserTokenService.cs
Explicit Debt · Dead code: UpdateScheduleTaskStatusAsync Domain/NexusStack.Core/Services/Schedules/ScheduleTaskService.cs
Explicit Debt · Dead code: EnumService Domain/NexusStack.Core/Services/SystemManagement/EnumService.cs
Explicit Debt · Dead code: GetSingleSettingForApiAsync Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs
Explicit Debt · Dead code: Entity Domain/NexusStack.EFCore/Entities/Entity.cs
Explicit Debt · Dead code: ExecuteSqlCommandAsync Domain/NexusStack.EFCore/Repository/Base/IRepositoryBase.cs
Explicit Debt · Dead code: ExecuteSqlCommandAsync Domain/NexusStack.EFCore/Repository/Base/IRepositoryBase.cs
Explicit Debt · Dead code: ExecuteSqlCommandAsync Domain/NexusStack.EFCore/Repository/Base/IRepositoryBase.cs
Explicit Debt · Dead code: BatchSoftDeleteAsync Domain/NexusStack.EFCore/Repository/IServiceBase.cs
Explicit Debt · Dead code: GetIgnoreQueryFiltersExpandable Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs
Explicit Debt · Dead code: ExistsWithSoftDeleteAsync Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs
Explicit Debt · Dead code: GetCountAsync Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs
Explicit Debt · Dead code: GetCountAsync Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs
Explicit Debt · Dead code: GetFromRawSqlAsync Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs
Explicit Debt · Dead code: GetFromRawSqlAsync Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs
Explicit Debt · Dead code: GetFromRawSqlAsync Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs
Explicit Debt · Dead code: ExcelHelper Domain/NexusStack.Excel/ExcelHelper.cs
Explicit Debt · Dead code: EPPlusExtensions Domain/NexusStack.Excel/Export/EPPlusExtensions.cs
Explicit Debt · Dead code: ExcelDateFormat Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: ExcelCompareIncomePer Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: ExcelCompare Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: ExcelNegate Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: InsertPictureInHtml Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: Default Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: InsertProblem Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: DecimalDivision Domain/NexusStack.Excel/Export/ReportHelper.cs
Explicit Debt · Dead code: CompareValue Domain/NexusStack.Excel/Export/ReportHelper.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: 9 findings

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

License Compliance · Banned license: iTextSharp.LGPLv2.Core
Exception handling · Swallowed exception (caught, then discarded) Domain/NexusStack.Core/CurrentUser.cs
Exception handling · Swallowed exception (empty catch) Domain/NexusStack.RabbitMQ/Connection.cs
Exception handling · Swallowed exception (empty catch) Domain/NexusStack.RabbitMQ/EventSubscriber.cs
Exception handling · Swallowed exception (empty catch) Domain/NexusStack.RabbitMQ/EventSubscriber.cs
Exception handling · Swallowed exception (empty catch) Domain/NexusStack.RabbitMQ/EventSubscriber.cs
Exception handling · Swallowed exception (empty catch) Domain/NexusStack.RabbitMQ/EventSubscriber.cs
Exception handling · Swallowed exception (caught, then discarded) Domain/NexusStack.RabbitMQ/EventSubscriber.cs
Async & latency hygiene · Awaits without ConfigureAwait(false)

Rebuild cost: about €51,000 · Estimate

Cost to rebuild	€17,000 to €85,000, for 275 to 893 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem	Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 38. 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: 20,890 lines of product code
Comment lines	The estimate prices 18,229 lines. Comment lines count towards the size of 20,890 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 tests found finding(s) in Test Distribution.

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

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

Raises the score by about 8 points · Medium effort · REDACTED Scanning

Reconcile the README with reality: README.md runs `dotnet run --project Host\MyAwesomeProject.WebAPI`, but `Host/MyAwesomeProject.WebAPI` does not exist; README.md names `docker-compose.yml`, but no file or folder `docker-compose.yml` exists; README.md changes into `Host/MyProject.WebAPI`, but no such folder exists; README.md runs `dotnet run --project Host/MyProject.Gateway`, but `Host/MyProject.Gateway` does not exist; README.md names `Host/MyProject.Gateway/proxy-config.json`, but no file or folder `Host/MyProject.Gateway/proxy-config.json` exists.

Raises the score by about 5 points · Medium effort · Documentation accuracy

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 €51,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 29 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

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

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

If you do one thing first · First action

Resolve the 1 No tests found finding(s) in Test Distribution. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 Test Distribution 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.

79 modules, with 174 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 39 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 EFCore.DbContexts	2 EFCore.Entities	3 Infrastructure	4 Infrastructure.Dtos	5 Infrastructure.Enums	6 Infrastructure.Models	7 RabbitMQ.EventBus	8 Core.Dtos	9 Core.Dtos.DownloadCenter	10 Core.Dtos.Files	11 Core.Dtos.GlobalSettings	12 Core.Dtos.OpenAppConfigs	13 Core.Dtos.Regions	14 Core.Dtos.ScheduleTasks	15 Core.Entities.AsyncTasks	16 Core.Entities.Schedules	17 Core.Entities.SystemManagement	18 EFCore.Repository	20 Infrastructure.Options	21 Redis	22 Core.Dtos.Menus	23 Core.Dtos.Roles	24 Core.Entities.Users	26 Core.Services.OpenAppConfigs	27 Infrastructure.FileStroage	28 Core.Dtos.Permissions	29 Core.Dtos.Users	31 Core	33 Core.Services.Interfaces	38 Core.Services.SystemManagement	39 Core.Services.Users
1 EFCore.DbContexts
2 EFCore.Entities
3 Infrastructure
4 Infrastructure.Dtos
5 Infrastructure.Enums
6 Infrastructure.Models
7 RabbitMQ.EventBus
8 Core.Dtos				2	3	1
9 Core.Dtos.DownloadCenter					2	1
10 Core.Dtos.Files				2	2	2
11 Core.Dtos.GlobalSettings				1		1
12 Core.Dtos.OpenAppConfigs				1
13 Core.Dtos.Regions				1	2	2
14 Core.Dtos.ScheduleTasks				2	3	1
15 Core.Entities.AsyncTasks		1			1
16 Core.Entities.Schedules		3			1
17 Core.Entities.SystemManagement		8			8
18 EFCore.Repository	1
19 EFCore.Repository.Base	1
20 Infrastructure.Options					2
21 Redis			1			2
22 Core.Dtos.Menus				2	2	1											4
23 Core.Dtos.Roles				1	2	1											2
24 Core.Entities.Users		6			4												2
25 Core.EventData					1		3								2
26 Core.Services.OpenAppConfigs	4		4															8
27 Infrastructure.FileStroage			3		5	3													3
28 Core.Dtos.Permissions				1	2												1						2
29 Core.Dtos.Users				3	6	2																2	2
30 Core.Mapping																1							1
31 Core			3		1											1											1
32 Core.SeedData			8													8												8
33 Core.Services.Interfaces			1		6		1	3		2			2		2		2	14			5		1			2	4	1
34 Core.Filters			3				2												1										3
35 Core.Services.AsyncTasks	1		1				2								1			1											1
36 Core.Services.Schedules	2		2													1		2		1									2
37 Core.Services.SignalR			1												1														2
38 Core.Services.SystemManagement	7		8		3			4	1	2	6		2				3	8			4				1				7
39 Core.Services.Users	7		8		4												2	8	1	2	1		4			2	4	1	15
40 WebAPI.Controllers					4	1		5	2	1	3	6	5	4		1	1	2		4	5	4		4	1	3	10	1	24	1	1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 52% · Adequate · gated by X4 ·

The Good

D1 · .NET / C# Cyclomatic Complexity 8.7 D2 · .NET / C# Cognitive Complexity 6.7 D3 · .NET / C# God Classes 9.8 D4 · .NET / C# Code Duplication 9.5 D17 · .NET / C# Explicit Debt 6.6 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 X1 · Repo Async correctness 7.4 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 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 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X5 · Repo Nullable reference types 9.9

The Bad

IC1 · Repo Incompleteness & stubs 4.4 X18 · Repo Disposal-pattern correctness 5.4 X2 · Repo Cancellation propagation 4.8 X3 · Repo Exception handling 5.2

The Ugly

X20 · Repo Mistyped argument guard 3.3 X4 · Repo Structured logging 3.7

At a glance — Architecture · 78% · Strong ·

The Good

D5 · .NET / C# Coupling 9.4 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 6.9 D27 · .NET / C# Navigability 9.0 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 7.3 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.8

The Bad

AX2 · Repo Stateful singletons 5.3

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

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 9.5 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 10.0 D34 · .NET / C# Knowledge Freshness 9.3 M3 · Repo Folder & project structure 6.0

The Bad

M1 · Repo Documentation (README) 4.7

The Ugly

M2 · Repo Architecture documentation 3.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 29% · Weak · gated by D9, D13, P7, P10 ·

The Good

D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 8.2 P2 · Repo Observability 5.8 P8 · Repo Schema migrations 10.0

The Bad

P4 · Repo Deployment & Rollback 5.0

The Ugly

D13 · .NET / C# REDACTED Scanning 0.0 P10 · Repo Library API & versioning 2.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 60% · Adequate · gated by D28, S1 ·

The Good

D29 · .NET / C# Static Analysis (SAST) 7.0 D30 · .NET / C# Dependency Vulnerabilities 7.3 D31 · .NET / C# IaC & Container Security 8.2 D44 · .NET / C# Platform End-of-Life 10.0 C2 · Repo Access Controls 8.0 C3 · Repo Audit Trail 7.5 C4 · Repo Data Retention 9.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 Ugly

D28 · .NET / C# Secrets (history) 0.0 S1 · Repo Web-Security Posture 3.0

At a glance — Event-Driven · 54% · Adequate ·

The Bad

ED1 · Repo Handler temporal coupling 5.4

At a glance — Performance · 60% · Strong ·

The Good

PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.1 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
A07:2025 — Authentication Failures	23	High / Critical
A02:2025 — Security Misconfiguration	11	High / Critical
A05:2025 — Injection	7	Medium
A03:2025 — Software Supply Chain Failures	5	High / Critical

Roadmap

Immediately address critical security risks by resolving ten leaked secrets and fix the single missing test in the distribution pipeline. Simultaneously, correct the inaccurate README documentation to reflect the actual project structure and enforce stricter library visibility by making types internal by default. Finally, establish a formal process for documenting significant architectural decisions to ensure long-term maintainability and clarity.

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

Do this	Helps	Effort	Dimension
Resolve the 1 No tests found finding(s) in Test Distribution.	+8.3 pts	Low	Test Distribution
Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (3), REDACTED.	+8.1 pts	Medium	REDACTED Scanning
Reconcile the README with reality: README.md runs `dotnet run --project Host\MyAwesomeProject.WebAPI`, but `Host/MyAwesomeProject.WebAPI` does not exist; README.md names `docker-compose.yml`, but no file or folder `docker-compose.yml` exists; README.md changes into `Host/MyProject.WebAPI`, but no such folder exists; README.md runs `dotnet run --project Host/MyProject.Gateway`, but `Host/MyProject.Gateway` does not exist; README.md names `Host/MyProject.Gateway/proxy-config.json`, but no file or folder `Host/MyProject.Gateway/proxy-config.json` exists.	+4.9 pts	Medium	Documentation accuracy
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.	+3.4 pts	Medium	Library API & versioning
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+3.0 pts	Medium	Architecture documentation
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.	+2.8 pts	Medium	Outbound HTTP resilience
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with NexusStack.Template.csproj.	+1.0 pts	Low	Explicit Debt
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ApiAsyncExceptionFilter.cs, ProxyManagementController.cs.	+1.0 pts	Low	Explicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 103 files carrying findings, judged against the Template bar: 1% slop · 16% mixed · 83% near-clean.

File	Score	Band	Worst signal
REDACTED	0.3	Slop	REDACTED Scanning: Leaked secret: REDACTED
Domain/NexusStack.RabbitMQ/EventSubscriber.cs	3.9	Mixed	Explicit Debt: EmptyCatchBlock
Infrastructure/Utils/StringExtensions.cs	4.1	Mixed	Explicit Debt: EmptyCatchBlock
REDACTED	4.3	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	4.4	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	5.1	Mixed	Secrets (history): REDACTED: REDACTED
REDACTED	5.1	Mixed	Secrets (history): REDACTED: REDACTED
REDACTED	5.1	Mixed	Secrets (history): REDACTED: REDACTED
REDACTED	5.1	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	5.2	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs	5.4	Mixed	Explicit Debt: WriteOnlyPrivateField
Domain/NexusStack.Excel/Export/EPPlusExtensions.cs	6.0	Near-clean	Explicit Debt: Dead code: EPPlusExtensions
Domain/NexusStack.EFCore/Repository/Query/SqlQueryExtensions.cs	6.0	Near-clean	Explicit Debt: Dead code: GetFromQueryAsync2

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

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

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

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

Could not be resolved — 6

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

Methodology & how to trust this report

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

D1D2D3D4D5D6D9D13D14D15D16D17D18D21D24D26D27D28D29D30D31D34D35D44AX1AX10AX2AX3AX5AX6C2C3C4ED1ED5GD1IC1M1M2M3M4P10P2P4P7P8PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 441 of 465 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 · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ 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 01a161e7-9388-70fd-a100-9c75dfaa65f5.

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.

D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
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 (20,689 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"]`.
D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Host/NexusStack.WebAPI/appsettings.json`, `REDACTED`, `REDACTED`, `REDACTED`, `Host/NexusStack.Gateway/proxy-config.json` and 9 more did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Domain/NexusStack.Core/Authentication/RequestAuthenticationHandler.cs`, `Domain/NexusStack.Core/Authentication/RequestAuthenticationSignalRTokenHandler.cs`, `Domain/NexusStack.Core/Authentication/RequestAuthenticationTokenHandler.cs`, `Domain/NexusStack.Core/EventHandler/OperationLogEventHandler.cs`, `Domain/NexusStack.Core/Filters/OperationLogActionFilter.cs`, … (+56 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D39 IL Efficiency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
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. 146 further occurrence(s) are not listed individually; the score already reflects all 186.

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.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".

The LLM boundary

LLM-set scores this run (5): D21, D24, D26, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity8.7 / 10Strong✓ 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 8.7 / 10 · rule-coverage 100% · ceiling Prevented

8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EPPlusExtensions.SaveToExcel at 27.

EPPlusExtensions.SaveToExcel (cyclomatic 27)Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:34

EPPlusExtensions.SaveToExcel (cyclomatic 26)Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:174

ApiAsyncExceptionFilter.OnExceptionAsync (cyclomatic 21)Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:40

RequestAuthorizeFilter.OnAuthorizationAsync (cyclomatic 20)Domain/NexusStack.Core/Filters/RequestAuthorizeFilter.cs:34

NotificationEventHandler.HandleAsync (cyclomatic 19)Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:26

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

What to do

Bring the 8 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with EPPlusExtensions.SaveToExcel (cyclomatic 27), EPPlusExtensions.SaveToExcel (cyclomatic 26), ApiAsyncExceptionFilter.OnExceptionAsync (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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 Complexity6.7 / 10Adequate✓ 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 6.7 / 10 · rule-coverage 100% · ceiling Prevented

19 method(s) exceeded the cognitive complexity threshold of 15; the worst was EPPlusExtensions.SaveToExcel at 81.

EPPlusExtensions.SaveToExcel (cognitive 81)Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:34

EPPlusExtensions.SaveToExcel (cognitive 69)Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:174

ApiAsyncExceptionFilter.OnExceptionAsync (cognitive 40)Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:40

CronScheduleService.ExecuteAsync (cognitive 37)Domain/NexusStack.Core/Schedules/CronScheduleService.cs:63

ServiceBase.FillTableByReader (cognitive 32)Domain/NexusStack.EFCore/Repository/ServiceBase.cs:221

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

What to do

Bring the 5 bodies over 30 down to 30 or less in Cognitive Complexity — start with EPPlusExtensions.SaveToExcel (cognitive 81), EPPlusExtensions.SaveToExcel (cognitive 69), ApiAsyncExceptionFilter.OnExceptionAsync (cognitive 40). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 6.7 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
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.8 / 10Stronggated by 1 serious finding✓ 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.8 / 10 · rule-coverage 100% · ceiling Prevented

1 god class(es) detected.

TooManyMethods: QueryRepositoryDomain/NexusStack.EFCore/Repository/Query/QueryRepository.cs

What to do

Resolve the 1 TooManyMethods finding(s) in God Classes — start with QueryRepository.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.5 / 10Stronggated by 23 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.5 / 10 · rule-coverage 100% · ceiling Verified

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

Duplicated block (46 lines × 2) · ×2Domain/NexusStack.Core/Dtos/Menus/MenuDto.cs:35

Duplicated block (10 lines × 2) · ×2Infrastructure/Client/HttpClientService.cs:30

Duplicated block (7 lines × 2) · ×2Domain/NexusStack.EFCore/Repository/Mapping/IMappingRepository.cs:23

Duplicated block (11 lines × 3) · ×2Host/NexusStack.WebAPI/Controllers/RegionController.cs:217

Near-duplicate member pair (69 shared lines)Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:35

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

What to do

Resolve the 2 Duplicated block (46 lines × 2) finding(s) in Code Duplication — start with MenuDto.cs, EPPlusExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with HttpClientService.cs, EPPlusExtensions.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with IMappingRepository.cs, IQueryRepository.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.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

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

Layer violation: Domain → InfrastructureREDACTED:31

Off the main sequence: NexusStack.InfrastructureREDACTED:1

What to do

Resolve the 1 Layer violation finding(s) in Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Off the main sequence finding(s) in Coupling — start with REDACTED. — 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 39 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

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

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

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

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

No test suite found.

No tests found

What to do

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

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

Do you agree with this assessment?

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

6 secret(s) detected.

REDACTED

What to do

Resolve the 10 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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 267 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 51 direct `PackageReference`(s), and 199 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?

D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

17 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 86 of the 340 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Small-team knowledge concentration

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D17 · Explicit Debt6.6 / 10Adequate✓ 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 6.6 / 10 · rule-coverage 100% · ceiling Prevented

19 deducted debt markers + 101 dead symbols across 20689 LoC in the .NET projects (1.7/KLoC) → score 6.6.

EmptyCatchBlock · ×9Domain/NexusStack.RabbitMQ/Connection.cs:56

WriteOnlyPrivateField · ×2Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:28

NoWarnInCsprojNexusStack.Template.csproj:17

Dead code: FormAsync · ×101Infrastructure/Client/HttpClientService.cs:91

CommentedOutCode · ×7REDACTED:196

What to do

Resolve the 9 EmptyCatchBlock finding(s) in Explicit Debt — start with EventSubscriber.cs (5), Connection.cs (2), EventPublisher.cs. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ApiAsyncExceptionFilter.cs, ProxyManagementController.cs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with NexusStack.Template.csproj. — One of this dimension's main actionable groups (1 issue-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 Shape10.0 / 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

12 projects, 340 source files, 20689 hand-written lines of code (20689 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 3377 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 18 inter-project edges.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.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 ValueExemplary◐ Sampled · advisory

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

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

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

42 valuable / 1 redundant across 200 sampled comments; 1 shown with locations.

redundant commentInfrastructure/Utils/FileHelper.cs:30

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D26 · Project Cohesion6.9 / 10Adequate✓ 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 6.9 / 10 · rule-coverage 100% · ceiling Documented

2 of 13 projects flagged as possibly oversized/incoherent.

Split NexusStack.Core

Split NexusStack.Template

What to do

Resolve the 1 Split NexusStack.Core finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Split NexusStack.Template finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D27 · Navigability9.0 / 10Exemplary✓ 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 9.0 / 10 · rule-coverage 100% · ceiling Documented

91 % of calls cross a namespace and 10 % 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 layerHost/NexusStack.WebAPI/Controllers/GlobalSettingController.cs:14

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D28 · Secrets (history)0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

12 finding(s): 0 critical, 12 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 12 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (12 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)7.0 / 10Adequate✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

7 finding(s): 0 critical, 0 high, 7 medium, 0 low. semgrep hit a parse error in 61 file(s) — `Domain/NexusStack.Core/Authentication/RequestAuthenticationHandler.cs` (line 21, line 27), `Domain/NexusStack.Core/Authentication/RequestAuthenticationSignalRTokenHandler.cs` (line 17, line 23), `Domain/NexusStack.Core/Authentication/RequestAuthenticationTokenHandler.cs` (line 14, line 20), `Domain/NexusStack.Core/EventHandler/OperationLogEventHandler.cs` (lines 12–13, line 23), `Domain/NexusStack.Core/Filters/OperationLogActionFilter.cs` (line 23, line 25, line 31, …), … (+56 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 60 of those file(s) — `Domain/NexusStack.Core/Authentication/RequestAuthenticationHandler.cs`, `Domain/NexusStack.Core/Authentication/RequestAuthenticationSignalRTokenHandler.cs`, `Domain/NexusStack.Core/Authentication/RequestAuthenticationTokenHandler.cs`, `Domain/NexusStack.Core/EventHandler/OperationLogEventHandler.cs`, `Domain/NexusStack.Core/Filters/OperationLogActionFilter.cs`, … (+55 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 1 additional row(s) came from that pass. Only the header's own parameter list is unread in them.

REDACTED

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities7.3 / 10Adequategated by 4 critical findings✓ 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 7.3 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 4 high, 1 medium, 0 low.

REDACTED

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security8.2 / 10Adequategated by 4 critical findings✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

11 finding(s): 0 critical, 4 high, 4 medium, 3 low.

REDACTED

What to do

Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness9.3 / 10Exemplary✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Documented

7 of 86 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.cs. Counted over 86 of the 340 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×7Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.cs:1

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

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

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

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

Do you agree with this assessment?

AX2 · Stateful singletons5.3 / 10Adequate✓ 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.

`EventCodeManager` is a singleton (one shared instance) but mutates instance state outside any lock (_eventCodeMapping; e.g. `_eventCodeMapping` at line 15). — Domain/NexusStack.RabbitMQ/EventCodeManager.cs:7

What to do

Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.

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.

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

`IQueryRepository<TEntity, TKey>` declares 36 members under just 14 distinct name(s): `ApplySpecification`, `ApplySpecification`, `GetQueryable`, `GetQueryableIgnoreQueryFilters`, `GetExpandable`, `GetIgnoreQueryFiltersExpandable`, `GetListAsync`, `GetListAsync`, `GetListAsync`, `GetListAsync`, `GetPagedListAsync`, `GetPagedListAsync`, `GetPagedListAsync`, `GetPagedListAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `ExistsAsync`, `ExistsWithSoftDeleteAsync`, `ExistsAsync`, `GetCountAsync`, `GetCountAsync`, `GetLongCountAsync`, `GetLongCountAsync`, `GetFromRawSqlAsync`, `GetFromRawSqlAsync`, `GetFromRawSqlAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 36 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 36 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:15
`IRedisService` declares 17 members under just 14 distinct name(s): `PingAsync`, `GetAsync`, `SetAsync`, `SetAsync`, `SetAsync`, `DeleteAsync`, `ScanAsync`, `SAddAsync`, `SRemAsync`, `SMembersAsync`, `SIsMemberAsync`, `HSetAsync`, `HGetAsync`, `HGetAllAsync`, `HGetAllAsync`, `HDelAsync`, `HExistsAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — Domain/NexusStack.Redis/IRedisService.cs:9

What to do

Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.

Do you agree with this assessment?

C2 · Access Controls8.0 / 10Strong✓ 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.

[AllowAnonymous] (4) outweighs [Authorize] (2) — review whether the open surface is intended.

What to do

Review the [AllowAnonymous] surface — keep anonymous endpoints deliberate and documented so the open surface stays intentional.

Do you agree with this assessment?

C3 · Audit Trail7.5 / 10Strong✓ Tool-verified

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

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

An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.

What to do

Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.

Do you agree with this assessment?

C4 · Data Retention9.0 / 10Exemplary✓ Tool-verified

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

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

A retention mechanism is present, but the data-lifecycle is not yet complete — missing: 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?

ED1 · Handler temporal coupling5.4 / 10Adequate✓ Tool-verified

Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).

Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.

`NotificationEventHandler.HandleAsync` makes a synchronous remote call (an HTTP call) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. — Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:26

What to do

Remove synchronous remote calls from message handlers — react by publishing further messages, so services stay temporally decoupled.

Do you agree with this assessment?

ED5 · Idempotency8.2 / 10Exemplary◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

`Schedules.CronScheduleService.ExecuteAsync` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Domain/NexusStack.Core/Schedules/CronScheduleService.cs:63

What to do

Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.

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. (×14) — Infrastructure/FileStroage/AliyunFileStorage.cs:134, Infrastructure/FileStroage/AliyunFileStorage.cs:140, Infrastructure/FileStroage/AliyunFileStorage.cs:145, …

What to do

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs4.4 / 10Adequate✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

`ProcessAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Domain/NexusStack.Core/Schedules/FirstDayOfMonthSchedule.cs:28
`GetFilesByIds` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:69
`UploadAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — REDACTED:233, REDACTED:92
`UploadFromUrlAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:238
`GetSettingListAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:73
`GetSingleSettingForApiAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:88
`GetDefaltSettingAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:96
`CreatePdfInvoice` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Domain/NexusStack.Excel/PDFHelper.cs:65
`HealthTips` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Host/NexusStack.WebAPI/Controllers/HealthController.cs:18
`GetListAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Host/NexusStack.WebAPI/Controllers/OperationLogController.cs:23
`export` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Host/NexusStack.WebAPI/Controllers/OperationLogController.cs:81
The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — Infrastructure/Converters/JsonLongConverter.cs:23
`UploadAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — Infrastructure/FileStroage/AliyunFileStorage.cs:22, Infrastructure/FileStroage/AliyunFileStorage.cs:150
`GetAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Infrastructure/FileStroage/AliyunFileStorage.cs:134
`GetStorageBaseDirectory` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Infrastructure/FileStroage/AliyunFileStorage.cs:140
`GetAbsolutePath` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — Infrastructure/FileStroage/AliyunFileStorage.cs:145
`UploadConfigAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Infrastructure/FileStroage/AliyunFileStorage.cs:192
`LocalFileStorage` has 8 unfinished members out of 16 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — REDACTED:16
`GetConfigFile` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:46
`DoesObjectExist` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:97
`DeleteObject` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:102
`UploadConfigAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:107
`GeneratePresignedConfigUri` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:112
`GetDownloadCenterUri` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:122
`GetDownloadCenterFile` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:127
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×13) — Domain/NexusStack.Core/Mapping/ScheduleTaskMapping.cs:17, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:60, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:143, …

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

36 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

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 12 of 13 project(s) that lack one — worth up to 1.8 pts.
Review the README against recent changes; refresh the parts that drifted.

Do you agree with this assessment?

M2 · Architecture documentation3.0 / 10Weak✓ 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.

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.

Do you agree with this assessment?

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

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

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

Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

What to do

Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.

Do you agree with this assessment?

M4 · Documentation accuracy0.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.md runs `dotnet run --project Host\MyAwesomeProject.WebAPI`, but `Host/MyAwesomeProject.WebAPI` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:45
README.md names `docker-compose.yml`, but no file or folder `docker-compose.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:227
README.md changes into `Host/MyProject.WebAPI`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:396
README.md runs `dotnet run --project Host/MyProject.Gateway`, but `Host/MyProject.Gateway` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:406
README.md names `Host/MyProject.Gateway/proxy-config.json`, but no file or folder `Host/MyProject.Gateway/proxy-config.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:411
README.md runs `dotnet ef migrations add InitialCreate --project Domain/MyProject.EFCore`, but `Domain/MyProject.EFCore` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:462
README.md runs `docker build -t myproject:latest -f Host/MyProject.WebAPI/Dockerfile .`, but `Host/MyProject.WebAPI/Dockerfile` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:470
Docs/superpowers/specs/2026-04-22-mapster-migration-design.md names `Domain/NexusStack.Core/MapProfiles/AutoMapperProfile.cs`, but no file or folder `Domain/NexusStack.Core/MapProfiles/AutoMapperProfile.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/superpowers/specs/2026-04-22-mapster-migration-design.md:84
Docs/superpowers/specs/2026-04-22-mapster-migration-design.md names `Domain/NexusStack.EFCore/Repository/AutoMapper/AutoMapperRepository.cs`, but no file or folder `Domain/NexusStack.EFCore/Repository/AutoMapper/AutoMapperRepository.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/superpowers/specs/2026-04-22-mapster-migration-design.md:86

What to do

Reconcile the README with reality: README.md runs `dotnet run --project Host\MyAwesomeProject.WebAPI`, but `Host/MyAwesomeProject.WebAPI` does not exist; README.md names `docker-compose.yml`, but no file or folder `docker-compose.yml` exists; README.md changes into `Host/MyProject.WebAPI`, but no such folder exists; README.md runs `dotnet run --project Host/MyProject.Gateway`, but `Host/MyProject.Gateway` does not exist; README.md names `Host/MyProject.Gateway/proxy-config.json`, but no file or folder `Host/MyProject.Gateway/proxy-config.json` exists.

Do you agree with this assessment?

P10 · Library API & versioning2.0 / 10Weak✓ Tool-verified

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

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

405/410 types (99%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.

What to do

Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
Stamp a semantic version (csproj <Version> or GitVersion/MinVer) and follow semver for breaking changes.

Do you agree with this assessment?

P2 · Observability5.8 / 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 7/12 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 12, 4 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
`Domain/NexusStack.Core/Schedules/CronScheduleService.cs` reports through `Console.Write…` at line 84 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/Schedules/CronScheduleService.cs:84, Domain/NexusStack.Core/Schedules/CronScheduleService.cs:84
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 376 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:376, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:376
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 377 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:377, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:377
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 378 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:378, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:378
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 390 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:390, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:390
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 391 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:391, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:391
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 398 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:398, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:398
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 404 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:404, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:404
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 471 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:471, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:471
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 482 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:482, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:482
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 483 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:483, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:483
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 514 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:514, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:514
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 534 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:534, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:534
`Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 553 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. (×2) — Domain/NexusStack.Core/ServiceCollectionExtensions.cs:553, Domain/NexusStack.Core/ServiceCollectionExtensions.cs:553

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.
Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

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.

Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.

What to do

Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Add an approval/environment gate (required reviewers / protection rules) before production promotion.

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.AddHttpClient<HttpClientService>()` 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). (×2) — Infrastructure/Client/HttpClientServiceExtensions.cs:13, Infrastructure/Client/HttpClientServiceExtensions.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?

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

Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

PF2 · Allocation hygiene6.1 / 10Strong✓ Tool-verified

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

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

What to do

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

Do you agree with this assessment?

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

4 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). (×4) — Domain/NexusStack.Core/Gateway/DynamicProxyConfigProvider.cs:66, Domain/NexusStack.RabbitMQ/EventPublisher.cs:34, Domain/NexusStack.RabbitMQ/EventSubscriber.cs:51, …

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 Posture3.0 / 10Weak✓ 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.

`md5Hasher.ComputeHash(…)` puts the password `password` through a fast general-purpose digest, so a stolen hash is guessed at billions of candidates a second whether or not it is salted — no key-derivation function (PBKDF2/scrypt/Argon2/bcrypt) stands between the password and the stored value. — Infrastructure/Utils/EncryptionHelp.cs:36
`user.Password != oldPasswordEncoded` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again. — Domain/NexusStack.Core/Services/Users/UserService.cs:107
MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. (×3) — Infrastructure/Utils/EncryptionHelp.cs:34, Infrastructure/Utils/EncryptionHelp.cs:19, Infrastructure/Utils/EncryptionHelp.cs:195
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. (×4) — BackgroundServices/NexusStack.MQService/Program.cs:8, BackgroundServices/NexusStack.PlanTaskService/Program.cs:8, Host/NexusStack.Gateway/Program.cs:7, …

What to do

Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `Infrastructure/Utils/EncryptionHelp.cs:36`.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `Infrastructure/Utils/EncryptionHelp.cs:19` (MD5), `Infrastructure/Utils/EncryptionHelp.cs:34` (MD5CryptoServiceProvider), `Infrastructure/Utils/EncryptionHelp.cs:195` (MD5). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.

Do you agree with this assessment?

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

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. (×4) — Domain/NexusStack.Core/Gateway/DynamicProxyConfigProvider.cs:66, Domain/NexusStack.RabbitMQ/EventPublisher.cs:34, Domain/NexusStack.RabbitMQ/EventSubscriber.cs:51, …
`File.ReadAllBytes` blocks the thread on I/O while `File.ReadAllBytesAsync` exists to wait without one — inside a method that is already `async`, await the twin. — Domain/NexusStack.Excel/PDFHelper.cs:81

What to do

Sync-over-async (deadlock risk)

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.4 / 10Adequate✓ 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.

`md5Hasher` is a `MD5CryptoServiceProvider`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `MD5Encrypt` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5Hasher = …;`), which releases it at the end of the scope on every path including a throw. — Infrastructure/Utils/EncryptionHelp.cs:34
`md5` is a `MD5`, which implements `IDisposable`, and it is created here (line 195). Every use of it in `SignMD5Request` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5 = …;`), which releases it at the end of the scope on every path including a throw. — Infrastructure/Utils/EncryptionHelp.cs:195
`workbook` is a `IWorkbook`, which implements `IDisposable`, and it is created here (line 23). Every use of it in `ExportToExcel` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var workbook = …;`), which releases it at the end of the scope on every path including a throw. — Domain/NexusStack.Excel/ExportStream/ExportExcelHelper.cs:23
`serviceProvider.CreateAsyncScope()` (line 44) creates an `IServiceScope`, and it is dropped: `CreateScope().ServiceProvider` never names the scope, so nothing can release it. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`. — Domain/NexusStack.Serilog/LoggerExtensions.cs:44

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 propagation4.8 / 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 33/214 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×39) — REDACTED:20, REDACTED:51, Infrastructure/Video/VideoHelper.cs:23, …

What to do

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

Do you agree with this assessment?

X20 · Mistyped argument guard3.3 / 10Weak✓ Tool-verified

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

The guard on line 310 rejects `sql` and line 312 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:312
The guard on line 322 rejects `sql` and line 324 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:324
The guard on line 333 rejects `sql` and line 335 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:335
The guard on line 27 rejects `sql` and line 29 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Domain/NexusStack.EFCore/Repository/Query/SqlQueryExtensions.cs:29
The guard on line 149 rejects `sql` and line 151 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Domain/NexusStack.EFCore/Repository/Query/SqlQueryExtensions.cs:151
The guard on line 36 rejects `TemplatePath` and line 38 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(TemplatePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `TemplatePath`, and on that path `TemplatePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Domain/NexusStack.Excel/Export/ExcelTemplateRender.cs:38

What to do

Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.

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

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — Infrastructure/Utils/EncryptionHelp.cs:66, Infrastructure/Utils/EncryptionHelp.cs:88
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. (×3) — Infrastructure/Utils/StringExtensions.cs:207, Domain/NexusStack.RabbitMQ/Connection.cs:56, Domain/NexusStack.RabbitMQ/EventSubscriber.cs:305
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). (×6) — Domain/NexusStack.RabbitMQ/Connection.cs:156, Domain/NexusStack.RabbitMQ/EventPublisher.cs:290, Domain/NexusStack.RabbitMQ/EventSubscriber.cs:80, …

What to do

Swallowed exception (caught, then discarded)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×33) — Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:41, Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:129, Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:84, …

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 `expandoObject`: line 30 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 42 then dereferences it directly with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `expandoObject` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Infrastructure/Utils/CollectExtensions.cs:42
~0.1 `!` suppressions per 1k syntax nodes — 17 suppression(s) across the 113432 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	52%	Adequate — gated by X4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	78%	Strong	Strongest area.
Maturity	34%	Adequate — gated by M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	29%	Weak — gated by D9, D13, P7, P10	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	60%	Adequate — gated by D28, S1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven	54%	Adequate	Acceptable, with room to improve.
Performance	60%	Strong	Solid.

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

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

SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 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.

C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo

Not included — 43 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 — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D19 Documentation Quality — LLM evaluation failed
D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 61 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the target did not build
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
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
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P1 CI/CD gates — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. Automated CI/CD gates are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
P12 CI test-gate honesty — no CI workflow found
P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 45 finding(s)

D28 · Secrets (history) · REDACTED · ×12

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

D13 · REDACTED Scanning · Leaked secret · ×10

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · EmptyCatchBlock · ×9

EmptyCatchBlock Domain/NexusStack.RabbitMQ/Connection.cs:56 — 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 Domain/NexusStack.RabbitMQ/Connection.cs:156 — 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 Domain/NexusStack.RabbitMQ/EventPublisher.cs:290 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:80 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:99 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:142 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:163 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:305 — 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 Infrastructure/Utils/StringExtensions.cs:207 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.

D30 · Dependency Vulnerabilities · High CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

D31 · IaC & Container Security · High IaC · ×4

REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · WriteOnlyPrivateField · ×2

WriteOnlyPrivateField Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:28 — private IOperationLogService operationLogService — 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 Host/NexusStack.Gateway/Controllers/ProxyManagementController.cs:12 — private ILogger<ProxyManagementController> _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.

S1 · Web-Security Posture · Password hashing without a KDF · ×2

Password hashing without a KDF Infrastructure/Utils/EncryptionHelp.cs:36 — `md5Hasher.ComputeHash(…)` puts the password `password` through a fast general-purpose digest, so a stolen hash is guessed at billions of candidates a second whether or not it is salted — no key-derivation function (PBKDF2/scrypt/Argon2/bcrypt) stands between the password and the stored value.
Password hashing without a KDF Domain/NexusStack.Core/Services/Users/UserService.cs:107 — `user.Password != oldPasswordEncoded` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. Store a salted KDF hash (PBKDF2/scrypt/Argon2/bcrypt) and verify by deriving again.

D17 · Explicit Debt · NoWarnInCsproj · ×1

NoWarnInCsproj NexusStack.Template.csproj:17 — NU5128 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.

D5 · Coupling · Layer violation · ×1

Layer violation: Domain → Infrastructure REDACTED:31 — NexusStack.Core (Domain) references NexusStack.Infrastructure (Infrastructure) — dependencies must point inward (Web → Application → Domain; Infrastructure implements inner interfaces, nothing depends outward on it).

Serious — 294 finding(s)

D17 · Explicit Debt · Dead code · ×101

Dead code: FormAsync Infrastructure/Client/HttpClientService.cs:91 — Method FormAsync — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: PostFormUrlEncodedAsync Infrastructure/Client/HttpClientService.cs:129 — Method PostFormUrlEncodedAsync — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: PostDingtalkMsgAsync Infrastructure/Client/HttpClientService.cs:211 — Method PostDingtalkMsgAsync — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: PostQyWinXinMsgAsync Infrastructure/Client/HttpClientService.cs:233 — Method PostQyWinXinMsgAsync — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: PostRequest Infrastructure/Client/RequestModel.cs:16 — NamedType PostRequest — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: XmlConverter Infrastructure/Converters/XmlConverter.cs:11 — NamedType XmlConverter — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetDownloadCenterUri Infrastructure/FileStroage/IFileStorage.cs:46 — Method GetDownloadCenterUri — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetFile Infrastructure/FileStroage/IFileStorage.cs:72 — Method GetFile — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetConfigFile Infrastructure/FileStroage/IFileStorage.cs:79 — Method GetConfigFile — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: UploadConfigAsync Infrastructure/FileStroage/IFileStorage.cs:88 — Method UploadConfigAsync — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GeneratePresignedConfigUri Infrastructure/FileStroage/IFileStorage.cs:95 — Method GeneratePresignedConfigUri — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: SignalROptions Infrastructure/Options/SignalROptions.cs:10 — NamedType SignalROptions — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetRedisKeys Infrastructure/Utils/CollectExtensions.cs:17 — Method GetRedisKeys — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ConvertExpandoObject Infrastructure/Utils/CollectExtensions.cs:28 — Method ConvertExpandoObject — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: RebuilderMetaDataQueryParemeter Infrastructure/Utils/CollectExtensions.cs:59 — Method RebuilderMetaDataQueryParemeter — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CheckIdColumnAndAddRow Infrastructure/Utils/CollectExtensions.cs:80 — Method CheckIdColumnAndAddRow — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ObjectToMap Infrastructure/Utils/ConvertHelper.cs:56 — Method ObjectToMap — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetDocPathByFileName Infrastructure/Utils/DocsHelper.cs:46 — Method GetDocPathByFileName — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetMD5 Infrastructure/Utils/EncryptionHelp.cs:17 — Method GetMD5 — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: RsaEncrypt Infrastructure/Utils/EncryptionHelp.cs:116 — Method RsaEncrypt — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GenerateBatchNumber Infrastructure/Utils/EncryptionHelp.cs:161 — Method GenerateBatchNumber — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GenerateCainiaoSha256Signature Infrastructure/Utils/EncryptionHelp.cs:214 — Method GenerateCainiaoSha256Signature — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: FileHelper Infrastructure/Utils/FileHelper.cs:8 — NamedType FileHelper — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToRoundUp Infrastructure/Utils/MoneyExtensions.cs:17 — Method ToRoundUp — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToRoundDown Infrastructure/Utils/MoneyExtensions.cs:27 — Method ToRoundDown — Roslyn's SymbolFinder walked every project the solution loads, including NexusStack.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
+ 76 more in this group — see findings.md.

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

Async method without CancellationToken: UploadAsync REDACTED:20 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAsync REDACTED:51 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SnapshotAsync Infrastructure/Video/VideoHelper.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: TranscodeAsync Infrastructure/Video/VideoHelper.cs:53 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: IsH264Codec Infrastructure/Video/VideoHelper.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleAsync Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:26 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleAsync Domain/NexusStack.Core/EventHandler/OperationLogEventHandler.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReloadConfigAsync Domain/NexusStack.Core/Gateway/DynamicProxyConfigProvider.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadConfigAsync Domain/NexusStack.Core/Gateway/DynamicProxyConfigProvider.cs:70 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetConfigAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:68 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadConfigAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:117 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveConfigAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:170 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetRouteAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:202 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetClusterAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:208 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddOrUpdateRouteAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:214 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteRouteAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:235 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddOrUpdateClusterAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:253 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteClusterAsync Domain/NexusStack.Core/Gateway/JsonProxyConfigStore.cs:273 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UpdateCronTask Domain/NexusStack.Core/HostedServices/ExecuteSeedDataService.cs:33 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ApplyAsync Domain/NexusStack.Core/SeedData/MenuSeedData.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ApplyAsync Domain/NexusStack.Core/SeedData/PermissionSeedData.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ApplyAsync Domain/NexusStack.Core/SeedData/RegionSeedData.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ApplyAsync Domain/NexusStack.Core/SeedData/RoleSeedData.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ApplyAsync Domain/NexusStack.Core/SeedData/ScheduleTaskSeedData.cs:24 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ApplyAsync Domain/NexusStack.Core/SeedData/UserDepartmentSeedData.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
+ 14 more in this group — see findings.md.

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

Unfinished stub — throws NotImplementedException Infrastructure/FileStroage/AliyunFileStorage.cs:134 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Infrastructure/FileStroage/AliyunFileStorage.cs:140 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Infrastructure/FileStroage/AliyunFileStorage.cs:145 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:46 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:92 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:97 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:102 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:107 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:112 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:122 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:127 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:69 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:233 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:238 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

IC1 · Incompleteness & stubs · Unfinished stub · ×14

Unfinished stub — throws NotImplementedException REDACTED:69 — `GetFilesByIds` 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 REDACTED:233 — `UploadAsync` 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 REDACTED:238 — `UploadFromUrlAsync` 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 Infrastructure/FileStroage/AliyunFileStorage.cs:134 — `GetAsync` 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 Infrastructure/FileStroage/AliyunFileStorage.cs:140 — `GetStorageBaseDirectory` 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 Infrastructure/FileStroage/AliyunFileStorage.cs:145 — `GetAbsolutePath` 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 REDACTED:46 — `GetConfigFile` 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 REDACTED:92 — `UploadAsync` 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 REDACTED:97 — `DoesObjectExist` 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 REDACTED:102 — `DeleteObject` 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 REDACTED:107 — `UploadConfigAsync` 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 REDACTED:112 — `GeneratePresignedConfigUri` 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 REDACTED:122 — `GetDownloadCenterUri` 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 REDACTED:127 — `GetDownloadCenterFile` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.

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

Fake-async — async method never awaits Domain/NexusStack.Core/Schedules/FirstDayOfMonthSchedule.cs:28 — `ProcessAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:73 — `GetSettingListAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:88 — `GetSingleSettingForApiAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:96 — `GetDefaltSettingAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Domain/NexusStack.Excel/PDFHelper.cs:65 — `CreatePdfInvoice` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Host/NexusStack.WebAPI/Controllers/HealthController.cs:18 — `HealthTips` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Host/NexusStack.WebAPI/Controllers/OperationLogController.cs:23 — `GetListAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Host/NexusStack.WebAPI/Controllers/OperationLogController.cs:81 — `export` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Infrastructure/FileStroage/AliyunFileStorage.cs:22 — `UploadAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Infrastructure/FileStroage/AliyunFileStorage.cs:150 — `UploadAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Infrastructure/FileStroage/AliyunFileStorage.cs:192 — `UploadConfigAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

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

Swallowed exception (empty catch) Infrastructure/Utils/StringExtensions.cs:207 — 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) Domain/NexusStack.RabbitMQ/Connection.cs:56 — 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) Domain/NexusStack.RabbitMQ/Connection.cs:156 — 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) Domain/NexusStack.RabbitMQ/EventPublisher.cs:290 — 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) Domain/NexusStack.RabbitMQ/EventSubscriber.cs:80 — 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) Domain/NexusStack.RabbitMQ/EventSubscriber.cs:99 — 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) Domain/NexusStack.RabbitMQ/EventSubscriber.cs:142 — 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) Domain/NexusStack.RabbitMQ/EventSubscriber.cs:163 — 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) Domain/NexusStack.RabbitMQ/EventSubscriber.cs:305 — 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.

D17 · Explicit Debt · CommentedOutCode · ×7

CommentedOutCode REDACTED:196 — 5 consecutive commented-code lines
CommentedOutCode Domain/NexusStack.EFCore/Repository/ServiceBase.cs:280 — 5 consecutive commented-code lines
CommentedOutCode Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:75 — 7 consecutive commented-code lines
CommentedOutCode Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:90 — 3 consecutive commented-code lines
CommentedOutCode Domain/NexusStack.Core/Services/SystemManagement/RegionService.cs:53 — 4 consecutive commented-code lines
CommentedOutCode Host/NexusStack.WebAPI/Controllers/RegionController.cs:39 — 4 consecutive commented-code lines
CommentedOutCode Infrastructure/FileStroage/AliyunFileStorage.cs:54 — 4 consecutive commented-code lines

X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×6

Argument guard throws the exception its own condition disproves Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:312 — The guard on line 310 rejects `sql` and line 312 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:324 — The guard on line 322 rejects `sql` and line 324 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:335 — The guard on line 333 rejects `sql` and line 335 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Domain/NexusStack.EFCore/Repository/Query/SqlQueryExtensions.cs:29 — The guard on line 27 rejects `sql` and line 29 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Domain/NexusStack.EFCore/Repository/Query/SqlQueryExtensions.cs:151 — The guard on line 149 rejects `sql` and line 151 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(sql)` is true of a value that is NOT null: it is satisfied by an EMPTY `sql`, and on that path `sql` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Domain/NexusStack.Excel/Export/ExcelTemplateRender.cs:38 — The guard on line 36 rejects `TemplatePath` and line 38 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrWhiteSpace(TemplatePath)` is true of a value that is NOT null: it is satisfied by an EMPTY `TemplatePath`, and on that path `TemplatePath` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.

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

Sync-over-async blocking — 4 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 Domain/NexusStack.Core/Gateway/DynamicProxyConfigProvider.cs:66 — `.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 Domain/NexusStack.RabbitMQ/EventPublisher.cs:34 — `.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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:51 — `.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 Domain/NexusStack.RabbitMQ/ServiceCollectionExtensions.cs:52 — `.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).

D31 · IaC & Container Security · Medium IaC · ×4

REDACTED
REDACTED
REDACTED
REDACTED

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

Sync-over-async (deadlock risk) Domain/NexusStack.Core/Gateway/DynamicProxyConfigProvider.cs:66 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) Domain/NexusStack.RabbitMQ/EventPublisher.cs:34 — 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) Domain/NexusStack.RabbitMQ/EventSubscriber.cs:51 — 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) Domain/NexusStack.RabbitMQ/ServiceCollectionExtensions.cs:52 — 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.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

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

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

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

Disposable created and abandoned in the method that made it Infrastructure/Utils/EncryptionHelp.cs:34 — `md5Hasher` is a `MD5CryptoServiceProvider`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `MD5Encrypt` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5Hasher = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Infrastructure/Utils/EncryptionHelp.cs:195 — `md5` is a `MD5`, which implements `IDisposable`, and it is created here (line 195). Every use of it in `SignMD5Request` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var md5 = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Domain/NexusStack.Excel/ExportStream/ExportExcelHelper.cs:23 — `workbook` is a `IWorkbook`, which implements `IDisposable`, and it is created here (line 23). Every use of it in `ExportToExcel` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var workbook = …;`), which releases it at the end of the scope on every path including a throw.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

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

Duplicated block (46 lines × 2) Domain/NexusStack.Core/Dtos/Menus/MenuDto.cs:35 — Domain/NexusStack.Core/Dtos/Menus/MenuDto.cs:35-80 | Domain/NexusStack.Core/Entities/SystemManagement/Menu.cs:44-89 — before extracting anything, compare `Domain/NexusStack.Core/Dtos/Menus/MenuDto.cs` and `Domain/NexusStack.Core/Entities/SystemManagement/Menu.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (46 lines × 2) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:118 — Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:118-163 | Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:247-292 — 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 `Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:118` 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.

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

Duplicated block (10 lines × 2) Infrastructure/Client/HttpClientService.cs:30 — Infrastructure/Client/HttpClientService.cs:30-39 | Infrastructure/Client/HttpClientService.cs:180-189 — 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 `Infrastructure/Client/HttpClientService.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:44 — Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:44-53 | Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:183-192 — 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 `Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:44` 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 (7 lines × 2) · ×2

Duplicated block (7 lines × 2) Domain/NexusStack.EFCore/Repository/Mapping/IMappingRepository.cs:23 — Domain/NexusStack.EFCore/Repository/Mapping/IMappingRepository.cs:23-29 | Domain/NexusStack.EFCore/Repository/Mapping/IMappingRepository.cs:31-37 — 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 `Domain/NexusStack.EFCore/Repository/Mapping/IMappingRepository.cs:23` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:42 — Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:42-48 | Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:61-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:42` 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 (11 lines × 3) · ×2

Duplicated block (11 lines × 3) Host/NexusStack.WebAPI/Controllers/RegionController.cs:217 — Host/NexusStack.WebAPI/Controllers/RegionController.cs:217-227 | Host/NexusStack.WebAPI/Controllers/ScheduleTaskController.cs:35-45 | Host/NexusStack.WebAPI/Controllers/SeedDataTaskController.cs:36-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Host/NexusStack.WebAPI/Controllers/RegionController.cs:217` 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 (11 lines × 3) Host/NexusStack.WebAPI/Controllers/RegionController.cs:239 — Host/NexusStack.WebAPI/Controllers/RegionController.cs:239-249 | Host/NexusStack.WebAPI/Controllers/ScheduleTaskController.cs:57-67 | Host/NexusStack.WebAPI/Controllers/SeedDataTaskController.cs:58-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Host/NexusStack.WebAPI/Controllers/RegionController.cs:239` 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.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2

Outbound HTTP without resilience Infrastructure/Client/HttpClientServiceExtensions.cs:13 — `services.AddHttpClient<HttpClientService>()` 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 Infrastructure/Client/HttpClientServiceExtensions.cs:37 — `services.AddHttpClient<HttpClientService>()` 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 (caught, then discarded) · ×2

Swallowed exception (caught, then discarded) Infrastructure/Utils/EncryptionHelp.cs:66 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) Infrastructure/Utils/EncryptionHelp.cs:88 — `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.

AX2 · Stateful singletons · Stateful singleton · ×1

Stateful singleton: EventCodeManager Domain/NexusStack.RabbitMQ/EventCodeManager.cs:7 — `EventCodeManager` is a singleton (one shared instance) but mutates instance state outside any lock (_eventCodeMapping; e.g. `_eventCodeMapping` at line 15).

D1 · Cyclomatic Complexity · EPPlusExtensions.SaveToExcel (cyclomatic 27) · ×1

EPPlusExtensions.SaveToExcel (cyclomatic 27) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:34 — EPPlusExtensions.SaveToExcel has cyclomatic complexity 27 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: Domain/NexusStack.Excel/Export/EPPlusExtensions.cs holds 2 of the 8 methods over the threshold — including the worst — and 23 of the 46 points over it (50%), 3.8× the next-largest file (Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs at 6). 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.

D1 · Cyclomatic Complexity · EPPlusExtensions.SaveToExcel (cyclomatic 26) · ×1

EPPlusExtensions.SaveToExcel (cyclomatic 26) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:174 — EPPlusExtensions.SaveToExcel has cyclomatic complexity 26 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: Domain/NexusStack.Excel/Export/EPPlusExtensions.cs holds 2 of the 8 methods over the threshold — including the worst — and 23 of the 46 points over it (50%), 3.8× the next-largest file (Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs at 6). 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.

D1 · Cyclomatic Complexity · ApiAsyncExceptionFilter.OnExceptionAsync (cyclomatic 21) · ×1

ApiAsyncExceptionFilter.OnExceptionAsync (cyclomatic 21) Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:40 — ApiAsyncExceptionFilter.OnExceptionAsync has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.

D1 · Cyclomatic Complexity · RequestAuthorizeFilter.OnAuthorizationAsync (cyclomatic 20) · ×1

RequestAuthorizeFilter.OnAuthorizationAsync (cyclomatic 20) Domain/NexusStack.Core/Filters/RequestAuthorizeFilter.cs:34 — RequestAuthorizeFilter.OnAuthorizationAsync has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · NotificationEventHandler.HandleAsync (cyclomatic 19) · ×1

NotificationEventHandler.HandleAsync (cyclomatic 19) Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:26 — NotificationEventHandler.HandleAsync has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · CronScheduleService.ExecuteAsync (cyclomatic 18) · ×1

CronScheduleService.ExecuteAsync (cyclomatic 18) Domain/NexusStack.Core/Schedules/CronScheduleService.cs:63 — CronScheduleService.ExecuteAsync has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PermissionService.ChangeRolePermissionAsync (cyclomatic 18) · ×1

PermissionService.ChangeRolePermissionAsync (cyclomatic 18) Domain/NexusStack.Core/Services/Users/PermissionService.cs:26 — PermissionService.ChangeRolePermissionAsync has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ExcelTemplateRender.ParseRow (cyclomatic 17) · ×1

ExcelTemplateRender.ParseRow (cyclomatic 17) Domain/NexusStack.Excel/Export/ExcelTemplateRender.cs:164 — ExcelTemplateRender.ParseRow has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · EPPlusExtensions.SaveToExcel (cognitive 81) · ×1

EPPlusExtensions.SaveToExcel (cognitive 81) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:34 — EPPlusExtensions.SaveToExcel has cognitive complexity 81 (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: Domain/NexusStack.Excel/Export/EPPlusExtensions.cs holds 2 of the 19 methods over the threshold — including the worst — and 120 of the 250 points over it (48%), 4.8× the next-largest file (Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs at 25). 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 · EPPlusExtensions.SaveToExcel (cognitive 69) · ×1

EPPlusExtensions.SaveToExcel (cognitive 69) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:174 — EPPlusExtensions.SaveToExcel has cognitive complexity 69 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Domain/NexusStack.Excel/Export/EPPlusExtensions.cs holds 2 of the 19 methods over the threshold — including the worst — and 120 of the 250 points over it (48%), 4.8× the next-largest file (Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs at 25). 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 · ApiAsyncExceptionFilter.OnExceptionAsync (cognitive 40) · ×1

ApiAsyncExceptionFilter.OnExceptionAsync (cognitive 40) Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:40 — ApiAsyncExceptionFilter.OnExceptionAsync has cognitive complexity 40 (threshold 15). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · CronScheduleService.ExecuteAsync (cognitive 37) · ×1

CronScheduleService.ExecuteAsync (cognitive 37) Domain/NexusStack.Core/Schedules/CronScheduleService.cs:63 — CronScheduleService.ExecuteAsync has cognitive complexity 37 (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 · ServiceBase.FillTableByReader (cognitive 32) · ×1

ServiceBase.FillTableByReader (cognitive 32) Domain/NexusStack.EFCore/Repository/ServiceBase.cs:221 — ServiceBase.FillTableByReader has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SqlQueryExtensions.GetFromQueryAsync2 (cognitive 30) · ×1

SqlQueryExtensions.GetFromQueryAsync2 (cognitive 30) Domain/NexusStack.EFCore/Repository/Query/SqlQueryExtensions.cs:79 — SqlQueryExtensions.GetFromQueryAsync2 has cognitive complexity 30 (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 · NotificationEventHandler.HandleAsync (cognitive 23) · ×1

NotificationEventHandler.HandleAsync (cognitive 23) Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:26 — NotificationEventHandler.HandleAsync has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · PermissionService.ChangeRolePermissionAsync (cognitive 23) · ×1

PermissionService.ChangeRolePermissionAsync (cognitive 23) Domain/NexusStack.Core/Services/Users/PermissionService.cs:26 — PermissionService.ChangeRolePermissionAsync has cognitive complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TypeFinders.SearchTypes (cognitive 22) · ×1

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

D2 · Cognitive Complexity · ExcelTemplateRender.ParseRow (cognitive 20) · ×1

ExcelTemplateRender.ParseRow (cognitive 20) Domain/NexusStack.Excel/Export/ExcelTemplateRender.cs:164 — ExcelTemplateRender.ParseRow has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ExportExcelHelper.ExportToExcel (cognitive 20) · ×1

ExportExcelHelper.ExportToExcel (cognitive 20) Domain/NexusStack.Excel/ExportStream/ExportExcelHelper.cs:20 — ExportExcelHelper.ExportToExcel has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RequestAuthorizeFilter.OnAuthorizationAsync (cognitive 19) · ×1

RequestAuthorizeFilter.OnAuthorizationAsync (cognitive 19) Domain/NexusStack.Core/Filters/RequestAuthorizeFilter.cs:34 — RequestAuthorizeFilter.OnAuthorizationAsync has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ExcelReader.ReadAllRows (cognitive 19) · ×1

ExcelReader.ReadAllRows (cognitive 19) Domain/NexusStack.Excel/Import/ExcelReader.cs:65 — ExcelReader.ReadAllRows has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RequestAuthenticationHandler.HandleAuthenticateAsync (cognitive 17) · ×1

RequestAuthenticationHandler.HandleAuthenticateAsync (cognitive 17) Domain/NexusStack.Core/Authentication/RequestAuthenticationHandler.cs:29 — RequestAuthenticationHandler.HandleAuthenticateAsync has cognitive complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MainSaveChangeInterceptor.AuditHandler (cognitive 17) · ×1

MainSaveChangeInterceptor.AuditHandler (cognitive 17) Domain/NexusStack.EFCore/MainSaveChangeInterceptor.cs:78 — MainSaveChangeInterceptor.AuditHandler has cognitive complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SqlQueryExtensions.GetFromQueryAsync (cognitive 17) · ×1

SqlQueryExtensions.GetFromQueryAsync (cognitive 17) Domain/NexusStack.EFCore/Repository/Query/SqlQueryExtensions.cs:20 — SqlQueryExtensions.GetFromQueryAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ExcelTemplateRender.ParseStatement (cognitive 17) · ×1

ExcelTemplateRender.ParseStatement (cognitive 17) Domain/NexusStack.Excel/Export/ExcelTemplateRender.cs:105 — ExcelTemplateRender.ParseStatement has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FileService.GetExportFiles (cognitive 16) · ×1

FileService.GetExportFiles (cognitive 16) REDACTED:255 — FileService.GetExportFiles has cognitive complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · EventSubscriber.OnConsumerMessageReceived (cognitive 16) · ×1

EventSubscriber.OnConsumerMessageReceived (cognitive 16) Domain/NexusStack.RabbitMQ/EventSubscriber.cs:395 — EventSubscriber.OnConsumerMessageReceived has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

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

REDACTED

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

REDACTED

D3 · God Classes · TooManyMethods · ×1

TooManyMethods: QueryRepository Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs — TooManyMethods — 200 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D30 · Dependency Vulnerabilities · Medium CVE · ×1

REDACTED

D4 · Code Duplication · Near-duplicate member pair (69 shared lines) · ×1

Near-duplicate member pair (69 shared lines) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:35 — Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:35-172 | Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:175-299 — These two members are variants of one another: 69 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

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

Duplicated block (47 lines × 2) Host/NexusStack.WebAPI/Controllers/OperationLogController.cs:26 — Host/NexusStack.WebAPI/Controllers/OperationLogController.cs:26-72 | Host/NexusStack.WebAPI/Controllers/OperationLogController.cs:84-130 — 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.

D4 · Code Duplication · Duplicated block (36–40 lines × 2) · ×1

Duplicated block (36–40 lines × 2) Domain/NexusStack.Core/Services/SystemManagement/MenuService.cs:77 — Domain/NexusStack.Core/Services/SystemManagement/MenuService.cs:77-112 | Domain/NexusStack.Core/Services/SystemManagement/RegionService.cs:72-111 — 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 `Domain/NexusStack.Core/Services/SystemManagement/MenuService.cs:77` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `model` to `MenuTreeQueryDto` in one and `RegionTreeQueryDto` 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 (38 lines × 2) · ×1

Duplicated block (38 lines × 2) Domain/NexusStack.Core/Dtos/ApiResourceDto.cs:20 — Domain/NexusStack.Core/Dtos/ApiResourceDto.cs:20-57 | Domain/NexusStack.Core/Entities/SystemManagement/ApiResource.cs:24-61 — before extracting anything, compare `Domain/NexusStack.Core/Dtos/ApiResourceDto.cs` and `Domain/NexusStack.Core/Entities/SystemManagement/ApiResource.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

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

Duplicated block (26 lines × 3) Domain/NexusStack.EFCore/Repository/Mapping/MappingRepository.cs:53 — Domain/NexusStack.EFCore/Repository/Mapping/MappingRepository.cs:53-78 | Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:138-163 | Domain/NexusStack.EFCore/Repository/Query/QueryRepository.cs:185-210 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.

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

Duplicated block (21 lines × 2) Domain/NexusStack.Core/Authentication/RequestAuthenticationSignalRTokenHandler.cs:34 — Domain/NexusStack.Core/Authentication/RequestAuthenticationSignalRTokenHandler.cs:34-54 | Domain/NexusStack.Core/Authentication/RequestAuthenticationTokenHandler.cs:40-60 — 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.

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

Duplicated block (18 lines × 2) Domain/NexusStack.Excel/Import/ExcelDataRow.cs:37 — Domain/NexusStack.Excel/Import/ExcelDataRow.cs:37-54 | Domain/NexusStack.Excel/Import/ExcelDataRow.cs:59-76 — 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 `Domain/NexusStack.Excel/Import/ExcelDataRow.cs:37` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Duplicated block (16–17 lines × 3) Infrastructure/FileStroage/AliyunFileStorage.cs:93 — Infrastructure/FileStroage/AliyunFileStorage.cs:93-109 | Infrastructure/FileStroage/AliyunFileStorage.cs:116-132 | Infrastructure/FileStroage/AliyunFileStorage.cs:175-190 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Infrastructure/FileStroage/AliyunFileStorage.cs:93` 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 (14–16 lines × 3) · ×1

Duplicated block (14–16 lines × 3) Domain/NexusStack.Core/Services/SystemManagement/MenuService.cs:103 — Domain/NexusStack.Core/Services/SystemManagement/MenuService.cs:103-116 | Domain/NexusStack.Core/Services/SystemManagement/RegionService.cs:100-115 | Domain/NexusStack.Core/Services/SystemManagement/RegionService.cs:120-134 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Domain/NexusStack.Core/Services/SystemManagement/MenuService.cs:103` 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 (13 lines × 2) · ×1

Duplicated block (13 lines × 2) Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:89 — Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:89-101 | Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:218-230 — 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 `Domain/NexusStack.Excel/Export/EPPlusExtensions.cs:89` 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 (9–10 lines × 2) · ×1

Duplicated block (9–10 lines × 2) Domain/NexusStack.RabbitMQ/ServiceCollectionExtensions.cs:39 — Domain/NexusStack.RabbitMQ/ServiceCollectionExtensions.cs:39-47 | Domain/NexusStack.RabbitMQ/ServiceCollectionExtensions.cs:60-69 — 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 `Domain/NexusStack.RabbitMQ/ServiceCollectionExtensions.cs:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

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

Duplicated block (9 lines × 2) REDACTED:110 — REDACTED:110-118 | REDACTED:151-159 — 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.

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

Duplicated block (5 lines × 2) Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:49 — Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:49-53 | Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:70-74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:49` 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 (6 lines × 2) · ×1

Duplicated block (6 lines × 2) Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.cs:253 — Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.cs:253-258 | Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.cs:310-315 — 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 `Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.cs:253` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `model` to `AppWebhookConfigDto` in one and `AppEventConfigDto` 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 (5 lines × 3) · ×1

Duplicated block (5 lines × 3) Domain/NexusStack.EFCore/Repository/Mapping/IMappingRepository.cs:22 — Domain/NexusStack.EFCore/Repository/Mapping/IMappingRepository.cs:22-26 | Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:60-64 | Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:69-73 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: NexusStack.Infrastructure REDACTED:1 — NexusStack.Infrastructure: abstractness 0.18, instability 0.00, distance 0.82 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.

ED1 · Handler temporal coupling · Temporal coupling in handler · ×1

Temporal coupling in handler: NotificationEventHandler.HandleAsync Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:26 — `NotificationEventHandler.HandleAsync` makes a synchronous remote call (an HTTP call) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.

ED5 · Idempotency · Non-idempotent mutation · ×1

Non-idempotent mutation: Schedules.CronScheduleService.ExecuteAsync Domain/NexusStack.Core/Schedules/CronScheduleService.cs:63 — `Schedules.CronScheduleService.ExecuteAsync` mutates persistent state (a repository write) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.

IC1 · Incompleteness & stubs · Both branches are identical · ×1

Both branches are identical — the condition decides nothing Infrastructure/Converters/JsonLongConverter.cs:23 — The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.

IC1 · Incompleteness & stubs · Skeleton type · ×1

Skeleton type — most members are unfinished REDACTED:16 — `LocalFileStorage` has 8 unfinished members out of 16 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented.

M1 · Documentation (README) · README may be stale · ×1

README may be stale — 36 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

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 · Blocking `File.ReadAllBytes` inside an `async` method · ×1

Blocking `File.ReadAllBytes` inside an `async` method Domain/NexusStack.Excel/PDFHelper.cs:81 — `File.ReadAllBytes` blocks the thread on I/O while `File.ReadAllBytesAsync` exists to wait without one — inside a method that is already `async`, await the twin.

X18 · Disposal-pattern correctness · DI scope created and never disposed · ×1

DI scope created and never disposed Domain/NexusStack.Serilog/LoggerExtensions.cs:44 — `serviceProvider.CreateAsyncScope()` (line 44) creates an `IServiceScope`, and it is dropped: `CreateScope().ServiceProvider` never names the scope, so nothing can release it. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`.

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

Symbol treated as nullable, then dereferenced unguarded Infrastructure/Utils/CollectExtensions.cs:42 — This method contradicts itself about `expandoObject`: line 30 assigns it with `as IDictionary<string, object>`, which hands back null rather than throwing when the value is not a `IDictionary<string, object>`, but line 42 then dereferences it directly with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `expandoObject` once before the first use and handle the null case, or cast with `(IDictionary<string, object>)` so the failure is reported where it happens — rather than leaving the two readings side by side.

Minor — 126 finding(s)

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

Interpolated log message defeats structured logging Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:41 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Domain/NexusStack.Core/EventHandler/NotificationEventHandler.cs:129 — 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 Domain/NexusStack.Core/Filters/ApiAsyncExceptionFilter.cs:84 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Domain/NexusStack.Core/HostedServices/ExecuteSeedDataService.cs:123 — 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 Domain/NexusStack.Core/HostedServices/ExecuteSeedDataService.cs:132 — 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 Domain/NexusStack.Core/HostedServices/ExecuteSeedDataService.cs:140 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Domain/NexusStack.Core/HostedServices/ExecuteSeedDataService.cs:150 — 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 Domain/NexusStack.Core/HostedServices/InitApiResourceService.cs:86 — 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 Domain/NexusStack.Core/Middlewares/ExceptionHandlerMiddleware.cs:39 — 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 Domain/NexusStack.Core/Schedules/CronScheduleService.cs:78 — 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 Domain/NexusStack.Core/Schedules/CronScheduleService.cs:142 — 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 Domain/NexusStack.Core/Schedules/CronScheduleService.cs:159 — 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 Domain/NexusStack.Core/Schedules/CronScheduleService.cs:175 — 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 Domain/NexusStack.Core/Schedules/CronScheduleService.cs:178 — 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 Domain/NexusStack.Core/Schedules/CronScheduleService.cs:206 — 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 Domain/NexusStack.RabbitMQ/EventPublisher.cs:39 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:209 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:400 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:404 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:423 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:450 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:474 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:518 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:623 — 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 Domain/NexusStack.RabbitMQ/EventSubscriber.cs:649 — 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.
+ 8 more in this group — see findings.md.

P2 · Observability · Console output used as the logging channel · ×28

Console output used as the logging channel Domain/NexusStack.Core/Schedules/CronScheduleService.cs:84 — `Domain/NexusStack.Core/Schedules/CronScheduleService.cs` reports through `Console.Write…` at line 84 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:376 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 376 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:377 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 377 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:378 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 378 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:390 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 390 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:391 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 391 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:398 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 398 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:404 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 404 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:471 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 471 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:482 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 482 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:483 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 483 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:514 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 514 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:534 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 534 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:553 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 553 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/Schedules/CronScheduleService.cs:84 — `Domain/NexusStack.Core/Schedules/CronScheduleService.cs` reports through `Console.Write…` at line 84 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:376 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 376 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:377 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 377 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:378 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 378 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:390 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 390 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:391 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 391 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:398 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 398 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:404 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 404 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:471 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 471 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:482 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 482 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel Domain/NexusStack.Core/ServiceCollectionExtensions.cs:483 — `Domain/NexusStack.Core/ServiceCollectionExtensions.cs` reports through `Console.Write…` at line 483 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
+ 3 more in this group — see findings.md.

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

Commented-out code Domain/NexusStack.Core/Mapping/ScheduleTaskMapping.cs:17 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Domain/NexusStack.Core/ServiceCollectionExtensions.cs:60 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Domain/NexusStack.Core/ServiceCollectionExtensions.cs:143 — 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 Domain/NexusStack.Core/ServiceCollectionExtensions.cs:172 — 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 Domain/NexusStack.Core/ServiceCollectionExtensions.cs:202 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code Domain/NexusStack.Core/ServiceCollectionExtensions.cs:262 — 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 Domain/NexusStack.Core/ServiceCollectionExtensions.cs:267 — 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 Domain/NexusStack.Core/ServiceCollectionExtensions.cs:282 — 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 Domain/NexusStack.Core/ServiceCollectionExtensions.cs:552 — 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 Domain/NexusStack.Core/Services/Interfaces/IUserService.cs:48 — 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 Domain/NexusStack.Core/Services/SystemManagement/EnumService.cs:33 — 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 REDACTED:203 — 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 Domain/NexusStack.Core/Services/SystemManagement/GlobalSettingService.cs:75 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).

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

README/code drift README.md:45 — README.md runs `dotnet run --project Host\MyAwesomeProject.WebAPI`, but `Host/MyAwesomeProject.WebAPI` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:227 — README.md names `docker-compose.yml`, but no file or folder `docker-compose.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:396 — README.md changes into `Host/MyProject.WebAPI`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:406 — README.md runs `dotnet run --project Host/MyProject.Gateway`, but `Host/MyProject.Gateway` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:411 — README.md names `Host/MyProject.Gateway/proxy-config.json`, but no file or folder `Host/MyProject.Gateway/proxy-config.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:462 — README.md runs `dotnet ef migrations add InitialCreate --project Domain/MyProject.EFCore`, but `Domain/MyProject.EFCore` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:470 — README.md runs `docker build -t myproject:latest -f Host/MyProject.WebAPI/Dockerfile .`, but `Host/MyProject.WebAPI/Dockerfile` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/superpowers/specs/2026-04-22-mapster-migration-design.md:84 — Docs/superpowers/specs/2026-04-22-mapster-migration-design.md names `Domain/NexusStack.Core/MapProfiles/AutoMapperProfile.cs`, but no file or folder `Domain/NexusStack.Core/MapProfiles/AutoMapperProfile.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Docs/superpowers/specs/2026-04-22-mapster-migration-design.md:86 — Docs/superpowers/specs/2026-04-22-mapster-migration-design.md names `Domain/NexusStack.EFCore/Repository/AutoMapper/AutoMapperRepository.cs`, but no file or folder `Domain/NexusStack.EFCore/Repository/AutoMapper/AutoMapperRepository.cs` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

D34 · Knowledge Freshness · Orphaned file · ×7

Orphaned file Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.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 Domain/NexusStack.Core/SeedData/MenuSeedData.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 Domain/NexusStack.Core/SeedData/RegionSeedData.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 Host/NexusStack.WebAPI/Controllers/GlobalSettingController.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 Host/NexusStack.WebAPI/Controllers/AsyncTaskController.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 Domain/NexusStack.Core/SeedData/RoleSeedData.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.

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

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 BackgroundServices/NexusStack.MQService/Program.cs:8 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected BackgroundServices/NexusStack.PlanTaskService/Program.cs:8 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected Host/NexusStack.Gateway/Program.cs:7 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected Host/NexusStack.WebAPI/Program.cs:6 — 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.

D31 · IaC & Container Security · Low IaC · ×3

REDACTED
REDACTED
REDACTED

AX6 · Interface segregation · Fat interface · ×2

Fat interface: IQueryRepository<TEntity, TKey> (36 members) Domain/NexusStack.EFCore/Repository/Query/IQueryRepository.cs:15 — `IQueryRepository<TEntity, TKey>` declares 36 members under just 14 distinct name(s): `ApplySpecification`, `ApplySpecification`, `GetQueryable`, `GetQueryableIgnoreQueryFilters`, `GetExpandable`, `GetIgnoreQueryFiltersExpandable`, `GetListAsync`, `GetListAsync`, `GetListAsync`, `GetListAsync`, `GetPagedListAsync`, `GetPagedListAsync`, `GetPagedListAsync`, `GetPagedListAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetByIdAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `GetAsync`, `ExistsAsync`, `ExistsWithSoftDeleteAsync`, `ExistsAsync`, `GetCountAsync`, `GetCountAsync`, `GetLongCountAsync`, `GetLongCountAsync`, `GetFromRawSqlAsync`, `GetFromRawSqlAsync`, `GetFromRawSqlAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 36 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 36 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: IRedisService (17 members) Domain/NexusStack.Redis/IRedisService.cs:9 — `IRedisService` declares 17 members under just 14 distinct name(s): `PingAsync`, `GetAsync`, `SetAsync`, `SetAsync`, `SetAsync`, `DeleteAsync`, `ScanAsync`, `SAddAsync`, `SRemAsync`, `SMembersAsync`, `SIsMemberAsync`, `HSetAsync`, `HGetAsync`, `HGetAllAsync`, `HGetAllAsync`, `HDelAsync`, `HExistsAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.

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

Silent fallback default in catch Domain/NexusStack.Core/CurrentUser.cs:122 — `FindClaimValue` swallows every exception into `return string.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch Domain/NexusStack.RabbitMQ/EventSubscriber.cs:594 — `GetRetryCount` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.

X7 · Silent fallback defaults · Silent fallback default on parse failure · ×2

Silent fallback default on parse failure REDACTED:294 — `GetExportFiles` falls back to `"导出失败"` when `e.State == (int)FileState.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure Domain/NexusStack.Excel/Export/ReportHelper.cs:273 — `DecimalDivision` returns `string.Empty` when `decimal.TryParse(value.ToString(), out var decimalValue)` 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.

C2 · Access Controls · Anonymous-heavy surface · ×1

Anonymous-heavy surface — [AllowAnonymous] (4) outweighs [Authorize] (2) — review whether the open surface is intended.

C3 · Audit Trail · Partial audit-trail evidence · ×1

Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.

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 documented retention period / data-expiry.

D16 · Bus Factor · Small-team knowledge concentration · ×1

Small-team knowledge concentration — 17 file(s) are concentrated to one author — the ambient state with 2 active author(s), not 17 separate risks. The signal becomes meaningful as ownership spreads; no per-file action implied now.

D24 · Comment Value · redundant comment · ×1

redundant comment Infrastructure/Utils/FileHelper.cs:30 — "防止读取文件过大,1KB循环读取" — 删除 - '防止读取文件过大' 是 fs.Read 的 obvious gotcha; the 1KB loop is restated by Read's buffer and length.

D26 · Project Cohesion · Split NexusStack.Core · ×1

Split NexusStack.Core — A generic catch-all name that is huge (9k LoC) and sprawls across 41 unrelated namespaces like Services.Interfaces, Dtos.Users, Entities.SystemManagement, and more. Suggested:

D26 · Project Cohesion · Split NexusStack.Template · ×1

Split NexusStack.Template — Generic catch-all name that is huge (20k LoC) and sprawls across 77 namespaces like WebAPI.Controllers, Core.Dtos.Users, EFCore.Entities, and more. Suggested:

D27 · Navigability · Pass-through layer · ×1

Pass-through layer Host/NexusStack.WebAPI/Controllers/GlobalSettingController.cs:14 — GlobalSettingController: all 6 public methods forward their arguments unchanged to globalSettingService and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call globalSettingService directly, or give the layer a job.

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

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 7 of 86 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 86 of the 340 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: Domain/NexusStack.Core/SeedData/MenuSeedData.cs, Host/NexusStack.WebAPI/Controllers/OpenAppConfigController.cs, REDACTED, Domain/NexusStack.Core/SeedData/RegionSeedData.cs, Domain/NexusStack.Core/SeedData/RoleSeedData.cs, Host/NexusStack.WebAPI/Controllers/GlobalSettingController.cs, Host/NexusStack.WebAPI/Controllers/AsyncTaskController.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D8 · Code Coverage · No tests · ×1

No tests — template/sample — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.

D9 · Test Distribution · No tests found · ×1

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

M2 · Architecture documentation · No ADRs · ×1

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

M3 · Folder & project structure · No src/ separation · ×1

No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

P10 · Library API & versioning · Large public API surface · ×1

Large public API surface — 405/410 types (99%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.

P10 · Library API & versioning · No explicit versioning · ×1

No explicit versioning — No explicit version was found by any of the six routes this check reads: a `<Version>` or `<VersionPrefix>` property; a `GitVersion` or `MinVer` reference; the split Arcade spelling (`<MajorVersion>` AND `<MinorVersion>` together); a hand-written `[assembly: AssemblyVersion]` in source, with `bin/` and `obj/` excluded so the SDK's generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as `-p:Version=` / `-p:PackageVersion=` on a `dotnet build` or `dotnet pack` line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 7/12 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 12, 4 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 rollback/health safety · ×1

No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.

PF1 · Benchmark discipline · No performance benchmarks · ×1

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

X10 · Duplicated predicate · Duplicated predicate · ×1

Duplicated predicate Domain/NexusStack.EFCore/Repository/Mapping/MappingRepository.cs:58 — `primaryKeyName == null || primaryKeyType == null` appears character-identically in 2 files — Domain/NexusStack.EFCore/Repository/Mapping/MappingRepository.cs, Domain/NexusStack.EFCore/Repository/Query/QueryRepository.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.

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

Not all async methods take a CancellationToken — Only 33/214 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 — 17 suppression(s) across the 113432 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.

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-eced0bd7375646b2b3be9f24b027b435/history.json --exit-code 0 --source .	12	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-eced0bd7375646b2b3be9f24b027b435/tree.json --exit-code 0 --source .	6	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 .	7	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list NexusStack.sln package --vulnerable --include-transitive --format json	5	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	11	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 61 file(s) — `Domain/NexusStack.Core/Authentication/RequestAuthenticationHandler.cs`, `Domain/NexusStack.Core/Authentication/RequestAuthenticationSignalRTokenHandler.cs`, `Domain/NexusStack.Core/Authentication/RequestAuthenticationTokenHandler.cs`, `Domain/NexusStack.Core/EventHandler/OperationLogEventHandler.cs`, `Domain/NexusStack.Core/Filters/OperationLogActionFilter.cs`, … (+56 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — This is a dotnet-new template — it produces no released artifact to attest. Supply-chain provenance, signing and SBOM are deferred to the application you build from it (add SLSA provenance / cosign signing / an SBOM in your app's release pipeline).	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	none (no readable dependency manifest)	—	none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).	0	—

Run 01a161e7-9388-70fd-a100-9c75dfaa65f5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 17 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Phone — 9 field(s)

CurrentUser.CustomerPhone Domain/NexusStack.Core/CurrentUser.cs:86
AppNotificationConfigDto.Phones Domain/NexusStack.Core/Dtos/OpenAppConfigs/AppNotificationConfigDto.cs:17
CreateUserDto.Mobile Domain/NexusStack.Core/Dtos/Users/CreateUserDto.cs:34
UserDto.Mobile Domain/NexusStack.Core/Dtos/Users/UserDto.cs:17
UserQueryDto.Mobile Domain/NexusStack.Core/Dtos/Users/UserQueryDto.cs:54
AppNotificationConfig.Phones Domain/NexusStack.Core/Entities/OpenAppConfigs/AppNotificationConfig.cs:29
User.Mobile Domain/NexusStack.Core/Entities/Users/User.cs:18
Logistics.Phone Domain/NexusStack.Excel/Export/PDFOrderInvoiceDto.cs:64
ICurrentUser.CustomerPhone Infrastructure/ICurrentUser.cs:68

Email — 8 field(s)

CurrentUser.Email Domain/NexusStack.Core/CurrentUser.cs:65
CreateUserDto.Email Domain/NexusStack.Core/Dtos/Users/CreateUserDto.cs:40
UserContextCacheDto.Email Domain/NexusStack.Core/Dtos/Users/UserContextCacheDto.cs:18
UserDto.Email Domain/NexusStack.Core/Dtos/Users/UserDto.cs:62
UserQueryDto.Email Domain/NexusStack.Core/Dtos/Users/UserQueryDto.cs:49
UserTokenDto.Email Domain/NexusStack.Core/Dtos/Users/UserTokenDto.cs:24
User.Email Domain/NexusStack.Core/Entities/Users/User.cs:73
ICurrentUser.Email Infrastructure/ICurrentUser.cs:33

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 · 52% · Adequate · gated by X4 ·

At a glance — Architecture · 78% · Strong ·

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

At a glance — Readiness · 29% · Weak · gated by D9, D13, P7, P10 ·

At a glance — Security · 60% · Adequate · gated by D28, S1 ·

At a glance — Event-Driven · 54% · Adequate ·

At a glance — Performance · 60% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts