Public report of lamondlu/Library, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 09:37 UTC · Survey ID cd_ed29abb53f684b83b1d92c5443633a39

lamondlu/Library

Measured 22 October 2026, 09:30 UTC, at code version 6239735

Test distribution: not measuredBoundary Type-Coupling: not measured

Test distribution is not measured: No automated tests.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 21out of 100 Critical ⚠
CriticalWeakAdequateStrongExemplary
Down 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Event-Driven 100 Exemplary Architecture 88 Strong Performance 85 Strong Domain Modelling 57 Adequate Maturity 51 Adequate Code Health 48 Weak Accessibility 37 Weak Production Readiness 15 Critical Security and Compliance 7 Critical

A medium codebase: 78,828 lines of product code in 28 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Security and Compliance, 7

Findings by how serious they are

123 critical 429 serious 150 minor

8 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 09:30 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

89of 94 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
681of 702 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
94dimensions across 9 lenses, read from 78,828 lines of product code in 28 projects.
Chapters

Executive summary

lamondlu/Library scores 21 out of 100 and is rated Critical, while seven of its nine lenses score higher still: Event-Driven at 100, rated Exemplary, Architecture at 88 and Performance at 85, both rated Strong, Domain Modelling at 57 and Maturity at 51, both rated Adequate, and Code Health at 48 and Accessibility at 37, both rated Weak.

The score is lower than those seven because the weakest lens counts most, and here that is Security and Compliance, which scores 7 and is rated Critical. Its Secrets (history) dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 1 No automated tests finding(s) in Code Coverage and to resolve the 1 No tests found finding(s) in Test Distribution, and if Security and Compliance rose to 70, the score would rise from 21 to about 32.

123 findings are critical: 36 in Secrets (history), 25 in Forms & labels, 22 in Static Analysis (SAST), 14 in Secret Scanning, seven in Dependency Vulnerabilities, seven in Explicit Debt, six in IaC & Container Security, two in Page structure, one in Code Coverage, one in Domain ↔ infrastructure boundary, one in Project dependency cycles and one in Web-Security Posture.

Watchdog couldn't measure 4 dimensions in this code, among them Dependency Hygiene, Navigability and IL Efficiency, so they are left out of the score. The product code is 78,828 lines, which would take an estimated 0.9 person-years, around €140,000, to rebuild.

Code Health 48 Weak, capped by Cognitive Complexity and Async correctness Architecture 88 Strong Maturity 51 Adequate, capped by Knowledge Freshness and Architecture documentation Production Readiness 15 ⚠ Critical, capped by Code Coverage, Test Distribution, Secret Scanning, CI/CD gates, Observability and Security & performance tooling Security and Compliance 7 ⚠ Critical, capped by Secrets (history), Static Analysis (SAST), Data Protection, Access Controls and Web-Security Posture Domain Modelling 57 Adequate, capped by Strongly-typed ids and Encapsulated state Event-Driven 100 ★ Exemplary Accessibility 37 Weak, capped by Text alternatives, Forms & labels and Visual & motion safety Performance 85 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.
Security and Compliance 7 · counts for 45%Production Readiness 15 · counts for 25%Accessibility 37 · counts for 14%Code Health 48 · counts for 8%Maturity 51 · counts for 4%Domain Modelling 57 · counts for 2%Performance 85 · counts for 1%Architecture 88 · counts for 1%Event-Driven 100 · counts for 0%

If Security and Compliance rose from 7 to 70, the lowest score rated Strong, the score would rise from 21 to about 32.

Code composition: what the lines of code are
Business logic 14%Supporting code 86%
New since the last survey: 181 findings

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

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

Fixed since the last survey: 7 findings

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

  • Cyclomatic Complexity · jquery-1.10.2.matcherFromGroupMatchers (cyclomatic 34) src/Library.UI/Scripts/jquery-1.10.2.js
  • Cognitive Complexity · jquery-1.10.2.matcherFromGroupMatchers (cognitive 55) src/Library.UI/Scripts/jquery-1.10.2.js
  • Static Analysis (SAST) · Medium: REDACTED src/Library.Service.Identity/IdentityController.cs
  • Static Analysis (SAST) · Medium: REDACTED src/Library.Service.Inventory/BooksController.cs
  • Static Analysis (SAST) · Medium: REDACTED src/Library.Service.Logs/LogsController.cs
  • Static Analysis (SAST) · Medium: REDACTED src/Library.Service.Rental/RentalRecordsController.cs
  • Exception handling · Swallowed exception (caught, then discarded) src/Library.Infrastructure.InjectionFramework/InjectContainer.cs
Rebuild cost: about €140,000 · Estimate
Cost to rebuild€45,000 to €230,000, for 757 to 2,398 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problemVery 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 21. 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.
SizeMedium: 78,828 lines of product code
Comment linesThe estimate prices 78,660 lines. Comment lines count towards the size of 78,828 lines but aren't priced as work.

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 8 points · Low effort · Code Coverage
2
Resolve the 1 No tests found finding(s) in Test Distribution.
Raises the score by about 8 points · Low effort · Test Distribution
3
Resolve the 14 Leaked secret finding(s) in Secret Scanning — start with REDACTED (14).
Raises the score by about 8 points · Medium effort · Secret Scanning

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 €140,000 to build again, about 0.9 person-years of work. Its weakest lens is Security and Compliance, at 7 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
One cause behind 34 Domain Modelling findings · Common cause
34 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (5 findings) · Rich vs anemic model (4 findings) · Strongly-typed ids (25 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 1 No automated tests finding(s) in Code Coverage. 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 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.2 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 110,846 lines over the last 90 days, which is about 449,542 lines a year. At that pace, the extra work comes to an estimated 22.5 to 149.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

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.

arch Library.Domain.Core Core Library.Infrastructure.Core Core Library.Infrastructure.Core->Library.Domain.Core Library.Infrastructure.DataPersistence.Core.SQLServer SQLServer Library.Infrastructure.DataPersistence.Identity.SQLServer SQLServer Library.Infrastructure.DataPersistence.Identity.SQLServer->Library.Infrastructure.Core Library.Infrastructure.DataPersistence.Identity.SQLServer->Library.Infrastructure.DataPersistence.Core.SQLServer Library.Infrastructure.InjectionFramework InjectionFramework Library.Infrastructure.DataPersistence.Identity.SQLServer->Library.Infrastructure.InjectionFramework Library.Infrastructure.DataPersistence.Inventory.SQLServer SQLServer Library.Infrastructure.DataPersistence.Inventory.SQLServer->Library.Infrastructure.Core Library.Infrastructure.DataPersistence.Inventory.SQLServer->Library.Infrastructure.DataPersistence.Core.SQLServer Library.Infrastructure.DataPersistence.Inventory.SQLServer->Library.Infrastructure.InjectionFramework Library.Service.Inventory.Domain Domain Library.Infrastructure.DataPersistence.Inventory.SQLServer->Library.Service.Inventory.Domain Library.Infrastructure.DataPersistence.Rental.SQLServer SQLServer Library.Infrastructure.DataPersistence.Rental.SQLServer->Library.Infrastructure.Core Library.Infrastructure.DataPersistence.Rental.SQLServer->Library.Infrastructure.DataPersistence.Core.SQLServer Library.Infrastructure.DataPersistence.Rental.SQLServer->Library.Infrastructure.InjectionFramework Library.Service.Rental.Domain Domain Library.Infrastructure.DataPersistence.Rental.SQLServer->Library.Service.Rental.Domain Library.Infrastructure.EventStorage.MongoDB MongoDB Library.Infrastructure.EventStorage.MongoDB->Library.Infrastructure.Core Library.Infrastructure.EventStorage.MongoDB->Library.Infrastructure.InjectionFramework Library.Infrastructure.Logger.SQLServer SQLServer Library.Infrastructure.Logger.SQLServer->Library.Infrastructure.Core Library.Infrastructure.Logger.SQLServer->Library.Infrastructure.DataPersistence.Core.SQLServer Library.Infrastructure.Messaging.RabbitMQ RabbitMQ Library.Infrastructure.Messaging.RabbitMQ->Library.Domain.Core Library.Infrastructure.Messaging.RabbitMQ->Library.Infrastructure.InjectionFramework Library.Infrastructure.Messaging.SignalR SignalR Library.Infrastructure.Messaging.SignalR->Library.Domain.Core Library.Infrastructure.Messaging.SignalR->Library.Infrastructure.Core Library.Infrastructure.Operation.Consul Consul Library.Infrastructure.Operation.Core Core Library.Infrastructure.Operation.Consul->Library.Infrastructure.Operation.Core Library.Service.Handler Handler Library.Service.Handler->Library.Domain.Core Library.Service.Handler->Library.Infrastructure.Core Library.Service.Handler->Library.Infrastructure.DataPersistence.Identity.SQLServer Library.Service.Handler->Library.Infrastructure.DataPersistence.Inventory.SQLServer Library.Service.Handler->Library.Infrastructure.DataPersistence.Rental.SQLServer Library.Service.Handler->Library.Infrastructure.EventStorage.MongoDB Library.Service.Handler->Library.Infrastructure.InjectionFramework Library.Service.Handler->Library.Infrastructure.Logger.SQLServer Library.Service.Handler->Library.Infrastructure.Messaging.RabbitMQ Library.Service.Handler->Library.Infrastructure.Messaging.SignalR Library.Service.Identity Identity Library.Service.Identity->Library.Domain.Core Library.Service.Identity->Library.Infrastructure.DataPersistence.Identity.SQLServer Library.Service.Identity->Library.Infrastructure.InjectionFramework Library.Service.Identity->Library.Infrastructure.Messaging.RabbitMQ Library.Service.Identity->Library.Infrastructure.Operation.Consul Library.Service.Identity->Library.Infrastructure.Operation.Core Library.Service.Inventory Inventory Library.Service.Inventory->Library.Domain.Core Library.Service.Inventory->Library.Infrastructure.DataPersistence.Inventory.SQLServer Library.Service.Inventory->Library.Infrastructure.InjectionFramework Library.Service.Inventory->Library.Infrastructure.Messaging.RabbitMQ Library.Service.Inventory->Library.Infrastructure.Messaging.SignalR Library.Service.Inventory->Library.Infrastructure.Operation.Consul Library.Service.Inventory->Library.Infrastructure.Operation.Core Library.Service.Inventory->Library.Service.Inventory.Domain Library.Service.Inventory.Domain->Library.Domain.Core Library.Service.Inventory.Domain->Library.Infrastructure.Core Library.Service.Logs Logs Library.Service.Logs->Library.Infrastructure.Core Library.Service.Logs->Library.Infrastructure.InjectionFramework Library.Service.Logs->Library.Infrastructure.Logger.SQLServer Library.Service.Logs->Library.Infrastructure.Operation.Consul Library.Service.Logs->Library.Infrastructure.Operation.Core Library.Service.Rental Rental Library.Service.Rental->Library.Domain.Core Library.Service.Rental->Library.Infrastructure.DataPersistence.Rental.SQLServer Library.Service.Rental->Library.Infrastructure.InjectionFramework Library.Service.Rental->Library.Infrastructure.Messaging.RabbitMQ Library.Service.Rental->Library.Infrastructure.Messaging.SignalR Library.Service.Rental->Library.Infrastructure.Operation.Consul Library.Service.Rental->Library.Infrastructure.Operation.Core Library.Service.Rental->Library.Service.Rental.Domain Library.Service.Rental.Domain->Library.Domain.Core Library.Service.Rental.Domain->Library.Infrastructure.Core __more__ +8 more projects

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.

73 modules, with 119 dependencies between them. One loop runs through 4 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 33 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 Domain.Core.Commands2 Domain.Core.Messaging3 Domain.Core.Models4 Infrastructure.DataPersistence.Core.SQLServer5 Infrastructure.Operation.Core.Models6 Service.Identity.Domain.ViewModels7 Service.Inventory.Domain.DTOs8 Service.Rental.Domain.ViewModels9 UI.Controllers10 Domain.Core11 Infrastructure.Messaging.RabbitMQ12 Infrastructure.Messaging.SignalR13 Infrastructure.Operation.Core14 Service.Inventory.Domain.Commands15 Service.Inventory.Domain.ViewModels16 Domain.Core.DataAccessor17 Infrastructure.EventStorage.MongoDB18 Infrastructure.EventStorage.SQLServer19 Infrastructure.Logger.SQLServer20 Infrastructure.Operation.Consul21 Service.Identity.Domain22 Service.Inventory.Domain.Events23 Service.Rental.Domain.Events24 Service.Identity.Domain.DataAccessors25 Service.Inventory.Domain.DataAccessors26 Service.Rental.Domain.DataAccessors27 Infrastructure.DataPersistence.Identity.SQLServer28 Infrastructure.DataPersistence.Rental.SQLServer29 Service.Handler30 Service.Identity31 Service.Inventory.Domain.CommandHandlers32 Service.Inventory.Domain.EventHandlers33 Service.Rental34 Service.Rental.Domain.CommandHandlers35 Service.Rental.Domain.EventHandlers36 Service.Inventory.Domain37 Service.Rental.Domain38 Infrastructure.DataPersistence.Inventory.SQLServer39 Service.Inventory.DTOs40 Service.Inventory
1 Domain.Core.Commands
2 Domain.Core.Messaging
3 Domain.Core.Models
4 Infrastructure.DataPersistence.Core.SQLServer
5 Infrastructure.Operation.Core.Models
6 Service.Identity.Domain.ViewModels
7 Service.Inventory.Domain.DTOs
8 Service.Rental.Domain.ViewModels
9 UI.Controllers
10 Domain.Core121
11 Infrastructure.Messaging.RabbitMQ5
12 Infrastructure.Messaging.SignalR1
13 Infrastructure.Operation.Core2
14 Service.Inventory.Domain.Commands4
15 Service.Inventory.Domain.ViewModels1
16 Domain.Core.DataAccessor11
17 Infrastructure.EventStorage.MongoDB13
18 Infrastructure.EventStorage.SQLServer13
19 Infrastructure.Logger.SQLServer32
20 Infrastructure.Operation.Consul21
21 Service.Identity.Domain11
22 Service.Inventory.Domain.Events16
23 Service.Rental.Domain.Events11
24 Service.Identity.Domain.DataAccessors221
25 Service.Inventory.Domain.DataAccessors1421
26 Service.Rental.Domain.DataAccessors112
27 Infrastructure.DataPersistence.Identity.SQLServer213
28 Infrastructure.DataPersistence.Rental.SQLServer1113
29 Service.Handler1111222
30 Service.Identity12133
31 Service.Inventory.Domain.CommandHandlers56455
32 Service.Inventory.Domain.EventHandlers2614131213
33 Service.Rental1113
34 Service.Rental.Domain.CommandHandlers4322
35 Service.Rental.Domain.EventHandlers127656
36 Service.Inventory.Domain11511011
37 Service.Rental.Domain181144413
38 Infrastructure.DataPersistence.Inventory.SQLServer11431
39 Service.Inventory.DTOs1
40 Service.Inventory11433
Uses a module listed above itPart of a loopThe module itself
1 Domain.Core.Commands2 Domain.Core.Messaging3 Domain.Core.Models4 Infrastructure.DataPersistence.Core.SQLServer5 Infrastructure.Operation.Core.Models6 Service.Identity.Domain.ViewModels7 Service.Inventory.Domain.DTOs8 Service.Rental.Domain.ViewModels9 UI.Controllers10 Domain.Core11 Infrastructure.Messaging.RabbitMQ12 Infrastructure.Messaging.SignalR13 Infrastructure.Operation.Core14 Service.Inventory.Domain.Commands15 Service.Inventory.Domain.ViewModels16 Domain.Core.DataAccessor17 Infrastructure.EventStorage.MongoDB18 Infrastructure.EventStorage.SQLServer19 Infrastructure.Logger.SQLServer20 Infrastructure.Operation.Consul21 Service.Identity.Domain22 Service.Inventory.Domain.Events23 Service.Rental.Domain.Events24 Service.Identity.Domain.DataAccessors25 Service.Inventory.Domain.DataAccessors26 Service.Rental.Domain.DataAccessors27 Infrastructure.DataPersistence.Identity.SQLServer28 Infrastructure.DataPersistence.Rental.SQLServer29 Service.Handler30 Service.Identity31 Service.Inventory.Domain.CommandHandlers32 Service.Inventory.Domain.EventHandlers33 Service.Rental34 Service.Rental.Domain.CommandHandlers35 Service.Rental.Domain.EventHandlers36 Service.Inventory.Domain37 Service.Rental.Domain38 Infrastructure.DataPersistence.Inventory.SQLServer39 Service.Inventory.DTOs40 Service.InventoryDomain.Core.Commands1Domain.Core.Messaging2Domain.Core.Models3Infrastructure.DataPersistence.Core.SQLServer4Infrastructure.Operation.Core.Models5Service.Identity.Domain.ViewModels6Service.Inventory.Domain.DTOs7Service.Rental.Domain.ViewModels8UI.Controllers9Domain.Core10Infrastructure.Messaging.RabbitMQ11Infrastructure.Messaging.SignalR12Infrastructure.Operation.Core13Service.Inventory.Domain.Commands14Service.Inventory.Domain.ViewModels15Domain.Core.DataAccessor16Infrastructure.EventStorage.MongoDB17Infrastructure.EventStorage.SQLServer18Infrastructure.Logger.SQLServer19Infrastructure.Operation.Consul20Service.Identity.Domain21Service.Inventory.Domain.Events22Service.Rental.Domain.Events23Service.Identity.Domain.DataAccessors24Service.Inventory.Domain.DataAccessors25Service.Rental.Domain.DataAccessors26Infrastructure.DataPersistence.Identity.SQLServer27Infrastructure.DataPersistence.Rental.SQLServer28Service.Handler29Service.Identity30Service.Inventory.Domain.CommandHandlers31Service.Inventory.Domain.EventHandlers32Service.Rental33Service.Rental.Domain.CommandHandlers34Service.Rental.Domain.EventHandlers35Service.Inventory.Domain36Service.Rental.Domain37Infrastructure.DataPersistence.Inventory.SQLServer38Service.Inventory.DTOs39Service.Inventory4012151241111313322111161122114211122131113111122212133564552614131213111343221276561151101118114441311431111433+33 more modules (most-connected shown)

At a glance — Code Health · 48% · Weak · gated by D2, X1 ·

The Good
D3 · JavaScript God Classes 9.3 D4 · JavaScript Code Duplication 9.8 D17 · JavaScript Explicit Debt 8.6 D18 · JavaScript Solution Shape 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.8 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 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 X4 · Repo Structured logging 10.0
The Bad
D1 · JavaScript Cyclomatic Complexity 5.6 X3 · Repo Exception handling 5.4
The Ugly
D2 · JavaScript Cognitive Complexity 3.6 X1 · Repo Async correctness 1.1 X18 · Repo Disposal-pattern correctness 4.3 X2 · Repo Cancellation propagation 4.0

At a glance — Architecture · 88% · Strong ·

The Good
D5 · JavaScript Coupling 9.1 D6 · JavaScript Cohesion (LCOM4) 10.0 D26 · JavaScript Project Cohesion 10.0 D35 · JavaScript Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9
The Bad
AX10 · Repo Code composition 6.3

At a glance — Maturity · 51% · Adequate · gated by D34, M2 ·

The Good
D15 · JavaScript Churn × Complexity Hotspots 10.0 D21 · JavaScript Naming Consistency 8.0 D24 · JavaScript Comment Value 9.0 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 8.0
The Bad
M1 · Repo Documentation (README) 6.7
The Ugly
D19 · JavaScript Documentation Quality 4.0 D20 · JavaScript ADR Quality 0.0 D34 · JavaScript Knowledge Freshness 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 15% · Critical · gated by D8, D9, D13, P1, P2, P3 ·

The Good
D14 · JavaScript License Compliance 10.0 ED5 · Repo Idempotency 10.0 P7 · Repo Outbound HTTP resilience 10.0
The Bad
P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0
The Ugly
D8 · JavaScript Code Coverage 0.0 D13 · JavaScript Secret Scanning 0.0 P1 · Repo CI/CD gates 0.0 P2 · Repo Observability 1.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 7% · Critical · gated by D28, D29, C1, C2, S1 ·

The Good
D43 · JavaScript Malicious Dependencies 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Bad
D30 · JavaScript Dependency Vulnerabilities 5.1 D31 · JavaScript IaC & Container Security 6.3 D44 · JavaScript Platform End-of-Life 6.0
The Ugly
D28 · JavaScript Secrets (history) 0.0 D29 · JavaScript Static Analysis (SAST) 0.1 C1 · Repo Data Protection 0.0 C2 · Repo Access Controls 0.0 S1 · Repo Web-Security Posture 0.0 X24 · Repo Document value interpolated into markup unescaped 1.9

At a glance — Domain Modelling · 57% · Adequate · gated by DM2, DM5 ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 10.0 DM11 · Repo Constructible invalid state 8.2 DM12 · Repo Ambient inputs in the domain 9.8 DM6 · Repo Domain ↔ infrastructure boundary 7.6 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0
The Bad
DM4 · Repo Rich vs anemic model 6.5
The Ugly
DM2 · Repo Strongly-typed ids 3.0 DM5 · Repo Encapsulated state 3.2

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

The Good
ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0 ED3 · Repo Event naming 10.0 ED4 · Repo Outbox / dual-write 10.0

At a glance — Accessibility · 37% · Weak · gated by AC1, AC2, AC6 ·

The Good
AC4 · Repo Keyboard semantics 10.0 AC5 · Repo ARIA correctness 10.0
The Ugly
AC1 · Repo Text alternatives 1.0 AC2 · Repo Forms & labels 4.0 AC3 · Repo Page structure 4.8 AC6 · Repo Visual & motion safety 2.9 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 85% · Strong ·

The Good
PF3 · Repo Async & latency hygiene 8.5

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection61High / Critical
A07:2025 — Authentication Failures51High / Critical
A02:2025 — Security Misconfiguration23High / Critical
A03:2025 — Software Supply Chain Failures10High / Critical

Roadmap

Immediately resolve the 14 leaked secrets in REDACTED and establish automated testing to cover the entire codebase, including addressing the lack of test distribution. Strengthen data security by encrypting sensitive data at rest and managing keys in a vault, unless this is already handled by infrastructure. Finally, enforce strict access controls by applying default-deny authorization policies or imperative guards to all endpoints.

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

Do thisHelpsEffortDimension
Resolve the 1 No automated tests finding(s) in Code Coverage.+7.6 ptsLowCode Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.+7.6 ptsLowTest Distribution
Resolve the 14 Leaked secret finding(s) in Secret Scanning — start with REDACTED (14).+7.6 ptsMediumSecret Scanning
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Library.Service.Rental.csproj.+3.3 ptsLowPlatform End-of-Life
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).+6.1 ptsMediumData Protection
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.+6.1 ptsMediumAccess Controls
Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Library.Service.Identity/IdentityController.cs:17`.+6.1 ptsMediumWeb-Security Posture
Resolve the 36 High secret finding(s) in Secrets (history) — start with REDACTED (36).+6.0 ptsMediumSecrets (history)

File quality

Per-file score 0–10 — a quality signature. Of 72 files carrying findings, judged against the Production bar: 6% slop · 70% mixed · 24% near-clean.

FileScoreBandWorst signal
REDACTED0.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.6SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED3.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedSecret Scanning: Leaked secret: REDACTED
REDACTED4.4MixedSecrets (history): High secret: REDACTED
REDACTED4.6MixedSecrets (history): High secret: REDACTED
REDACTED4.6MixedSecrets (history): High secret: REDACTED
REDACTED5.1MixedSecrets (history): High secret: REDACTED
REDACTED5.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedSecret Scanning: Leaked secret: REDACTED
REDACTED5.8MixedSecret Scanning: Leaked secret: REDACTED
REDACTED5.8MixedSecret Scanning: Leaked secret: REDACTED

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

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

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

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

Could not be resolved — 8

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. 89 of 94 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.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 94 dimensions across the health lenses
D1D2D3D4D5D6D8D9D13D14D15D17D18D19D20D21D24D26D28D29D30D31D34D35D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX3AX4AX5AX6C1C2DM1DM10DM11DM12DM2DM4DM5DM6DM8DM9ED1ED2ED3ED4ED5GD1IC1M1M2M3M4P1P2P3P4P6P7PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4

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
  1. 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, 681 of 702 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.)
  2. 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.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.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 measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a162f2-ab48-76e8-aaf4-3be938b9ec8a.

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: error: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/WebApplications/Microsoft.WebApplication.targets" was not found. Confirm that the expression in the Import declaration "$(VSToolsPath)/WebApplications/Microsoft.WebApplication.targets", which evaluated to "/usr/….
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 254 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/Library.UI/Library.UI.csproj' with message: This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.Net.Compilers….
  • D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 7 deducted marker(s) and the 0.7/KLoC density on this row were taken over this repository's .NET projects ALONE: .js (70,899 lines, 90% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D18 Solution Shape — 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. `dotnet build` reported 3 error(s), and the diagnostics it printed were: MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/WebApplications/Microsoft.WebApplication.targets" was not found. Confirm that the expression in the Import declaration "$(VSToolsPath)/WebApplications/Microsoft.WebApplication.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/WebApplications/Microsoft.WebApplication.targets", is correct, and that the file exists on disk.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
  • 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 (78,828 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"]`.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • 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; `REDACTED`, `src/Library.Service.Logs/appsettings.Development.json`, `src/Library.ApiGateway/configuration.json`, `src/Library.ApiGateway/appsettings.json` 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.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (nuget REDACTED) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Library.UI/Scripts/_references.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via Dockerfile (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.
  • C2 Access Controls — 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. 2 further occurrence(s) are not listed individually; the score already reflects all 42.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • 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".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (5): D19, D21, D24, 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 Complexity5.6 / 10Adequate✓ 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 5.6 / 10 · rule-coverage 100% · ceiling Prevented

56 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was jquery-1.6.4.Sizzle at 51. A further 4 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being jquery-1.6.4.jQuery.each() at 21 — they are counted neither in the figure above nor in this dimension's score.

jquery-1.6.4.Sizzle (cyclomatic 51) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3715
jquery-1.6.4.liveHandler (cyclomatic 29) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3580
jquery-1.6.4.Sizzle.filter (cyclomatic 25) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3914
jquery-1.6.4.ajaxConvert (cyclomatic 21) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7423
jquery-1.6.4.getWH (cyclomatic 20) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6473

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

What to do

  1. Bring the 10 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with jquery-1.6.4.Sizzle (cyclomatic 51), jquery-1.6.4.Sizzle (cyclomatic 51), jquery-3.2.1.defaultPrefilter (cyclomatic 45). — 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 10 together lifts Cyclomatic Complexity from 5.6 to about 6.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity3.6 / 10Weak✓ 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 3.6 / 10 · rule-coverage 100% · ceiling Prevented

74 method(s) exceeded the cognitive complexity threshold of 15; the worst was jquery-3.2.1.defaultPrefilter at 81.

jquery-1.6.4.Sizzle.filter (cognitive 80) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3914
jquery-1.6.4.Sizzle (cognitive 79) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3715
jquery-1.6.4.ajaxConvert (cognitive 50) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7423
jquery-1.6.4.liveHandler (cognitive 45) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3580
jquery-1.6.4.dirCheck (cognitive 31) · ×2src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4982

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

What to do

  1. Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with jquery-3.2.1.defaultPrefilter (cognitive 81), jquery-1.6.4.Sizzle.filter (cognitive 80), jquery-1.6.4.Sizzle.filter (cognitive 80). — 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 Cognitive Complexity from 3.6 to about 4.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.3 / 10Stronggated by 12 serious findings✓ Tool-verified

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

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

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

12 over-large unit(s) detected — types, modules or files that carry too much.

FileTooLong: Scripts/jquery-1.10.2.js · ×10src/Library.UI/Scripts/jquery-1.10.2.js
FunctionTooLong: respond.getEmValue · ×2src/Library.UI/Scripts/respond.js:72

What to do

  1. Resolve the 10 FileTooLong finding(s) in God Classes — start with jquery-1.6.4.js (2), jquery.signalR-2.2.2.js (2), jquery-1.10.2.js. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 2 FunctionTooLong finding(s) in God Classes — start with respond.js, respond.matchmedia.addListener.js. — One of this dimension's main actionable groups (2 warning-level).
  3. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

37 duplicated block group(s) detected. Measured on part of this repository only: .js (90% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (17 lines × 2) · ×5REDACTED:83
Duplicated block (19 lines × 4) · ×3src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:23
Duplicated block (9 lines × 2) · ×3src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/Extensions/ConvertExtension.cs:23
Duplicated block (15 lines × 2) · ×2REDACTED:235
Duplicated block (10 lines × 2) · ×2REDACTED:151

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

What to do

  1. Resolve the 5 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with REDACTED (3), CommandLogModel.cs, UnreturnedBookViewModel.cs. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 3 Duplicated block (19 lines × 4) finding(s) in Code Duplication — start with ApiRequest.cs (3). — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ConvertExtension.cs, REDACTED, CommandHub.cs. — One of this dimension's main actionable groups (3 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling9.1 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

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

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

Off the main sequence: Library.Infrastructure.InjectionFramework · ×3src/Library.Infrastructure.InjectionFramework/Library.Infrastructure.InjectionFramework.csproj:1

What to do

  1. Resolve the 3 Off the main sequence finding(s) in Coupling — start with Library.Infrastructure.InjectionFramework.csproj, Library.Infrastructure.DataPersistence.Core.SQLServer.csproj, Library.Infrastructure.Core.csproj. — One of this dimension's main actionable groups (3 warning-level).
  2. Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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 20 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

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

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

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

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

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

No automated tests

What to do

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

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

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

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

D13 · Secret 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

5 secret(s) detected.

REDACTED

What to do

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

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

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

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 1 serious finding✓ 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

Top hotspots: src/Library.UI/Scripts/respond.js (3×30=90)

Hotspot: src/Library.UI/Scripts/respond.jssrc/Library.UI/Scripts/respond.js:97

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with respond.js. — One of this dimension's main actionable groups (1 warning-level).

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

D17 · Explicit Debt8.6 / 10Adequategated by 7 critical findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

7 deducted debt markers + unmeasured dead symbols across 7929 LoC in the .NET projects (0.7/KLoC) → score 8.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .js (90% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

EmptyCatchBlock · ×5src/Library.Infrastructure.EventStorage.MongoDB/MongoDBEventStorage.cs:117
WriteOnlyPrivateField · ×2src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:17

What to do

  1. Resolve the 5 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (2), MongoDBEventStorage.cs, SQLServerEventStorage.cs. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RabbitMQEventSubscriber.cs, IdentityController.cs. — One of this dimension's main actionable groups (2 issue-level).
  3. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D18 · Solution Shape9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

28 projects, 254 source files, 7929 hand-written lines of code (7929 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), 70 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.) Measured across 2 solutions loaded as one workspace: `src/Library.sln`, `src/Library.SignalR/Library.SignalR.sln`.

Thin analysable surface across projects: Library.Infrastructure.CSDataAccessor.Rentalsrc/Library.Infrastructure.CSDataAccessor.Rental/Library.Infrastructure.CSDataAccessor.Rental.csproj

✓ On the Gold path — maintain.

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

D19 · Documentation QualityWeak◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README is a single descriptive document covering the project scope (a microservice using .NET Core 2.0, DDD, CQRS, Event Sourcing, Redis and RabbitMQ), its components, prerequisites, EDA, service discovery, and an SelfRegister() example for one component, plus architecture diagrams pointing to external docs/Architecture folders. It is a thin README with no installation/build instructions, no usage examples, no contribution guidance, and no licence statement; the referenced Architecture/Docs markdown files are empty.

XML-doc coverage: Library.Service.Identity · ×28src/Library.Service.Identity/Library.Service.Identity.csproj

What to do

  1. Improve Documentation Quality — currently 4.0/10. — The repository's root README is a single descriptive document covering the project scope (a microservice using .NET Core 2.0, DDD, CQRS, Event Sourcing, Redis and RabbitMQ), its components, prerequisites, EDA, service discovery, and an SelfRegister() example for one component, plus architecture diagrams pointing to external docs/Architecture folders. It is a thin README with no installation/build instructions, no usage examples, no contribution guidance, and no licence statement; the referenced Architecture/Docs markdown files are empty.

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

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming ConsistencyStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Verified

2 naming inconsistencies across 200 sampled symbols.

Typo in event handler name: 'BookIssuedDatehangedEventHandler' is missing the 'C' in 'Changed', whereas similar handlers like 'BookISBNChangedEventHandler' and the event 'BookNameChangedEvent' use the correct spelling. This creates a visual inconsistency and potential maintenance confusion.
Spelling error in event name: 'CustomerOwnedBookExcceedEvent' contains a typo ('Excceed' with double 'e'), while other status/result events like 'BookInventoryOutputFailedEvent' and 'ReturnBookRequestSucceedEvent' are spelled correctly. This breaks the consistent vocabulary of event naming.

What to do

  1. Resolve the 1 Typo in event handler name finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Spelling error in event name finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

23 valuable / 0 redundant across 49 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

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

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

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

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

0 of 28 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

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: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

REDACTED
REDACTED

What to do

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

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

61 finding(s): 0 critical, 22 high, 19 medium, 20 low. semgrep hit a parse error in 7 file(s) — `src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js`, `src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js`, `src/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js`, `src/Library.SignalR/Scripts/jquery-1.6.4.js`, `src/Library.UI/Scripts/_references.js` (line 1), … (+2 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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D30 · Dependency Vulnerabilities5.1 / 10Adequate✓ 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 5.1 / 10 · rule-coverage 100% · ceiling Documented

10 finding(s): 0 critical, 7 high, 3 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget REDACTED), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security6.3 / 10Adequate✓ Tool-verified

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

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

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

23 finding(s): 0 critical, 6 high, 17 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 17 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 6 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).

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

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

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

21 of 21 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/InventoryReportDataAccessor.cs. Counted over 21 of the 254 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×21src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/InventoryReportDataAccessor.cs:1
Dormant codebase

What to do

  1. Resolve the 21 Orphaned file finding(s) in Knowledge Freshness — start with ApiRequest.cs (4), REDACTED (2), InventoryReportDataAccessor.cs. — One of this dimension's main actionable groups (21 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

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

End-of-life runtime: .NET netcoreapp2.0src/Library.Service.Rental/Library.Service.Rental.csproj:4

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with Library.Service.Rental.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • A <object> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — src/Library.UI/Scripts/jquery-1.10.2.js:5953

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×18) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:1164, src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5419, src/Library.SignalR/Scripts/jquery-1.6.4.js:1164, …
  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×7) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4758, src/Library.SignalR/Scripts/jquery-1.6.4.js:4758, src/Library.UI/Scripts/jquery-1.10.2.js:2914, …
  • A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×3) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5420, src/Library.SignalR/Scripts/jquery-1.6.4.js:5420, src/Library.UI/Scripts/jquery-1.10.2.js:5951

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure4.8 / 10Weak✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×5) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:1325, src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:8573, src/Library.SignalR/Scripts/jquery-1.6.4.js:1325, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — REDACTED:2, src/Library.UI/Views/Shared/_Layout.cshtml:4
  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — src/Library.UI/Scripts/jquery-1.10.2.js:7186
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×3) — src/Library.UI/Views/Account/ForgotPassword.cshtml:11, src/Library.UI/Views/Account/Register.cshtml:11, src/Library.UI/Views/Account/ResetPassword.cshtml:11
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — src/Library.UI/Views/Shared/_Layout.cshtml:4

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety2.9 / 10Weak✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.btn-success` sets color: #fff on background-color: #5cb85c — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Library.UI/Content/bootstrap.css:3173
  • `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:3518
  • `.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:3573
  • `.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:3592
  • `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:3717
  • `.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:4307
  • `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:5879
  • `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:5913
  • `.carousel-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/Library.UI/Content/bootstrap.css:6354
  • `.collapsing` moves (`transition-property: height, visibility`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Library.UI/Content/bootstrap.css:3500
  • `.progress-bar` moves (`transition: width .6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Library.UI/Content/bootstrap.css:5148
  • `.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Library.UI/Content/bootstrap.css:5162
  • `.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Library.UI/Content/bootstrap.css:5884
  • `.carousel-inner > .item` moves (`transition: .6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Library.UI/Content/bootstrap.css:6250
  • `.carousel-inner > .item` moves (`transition: transform .6s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Library.UI/Content/bootstrap.css:6260

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 33 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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.

AX10 · Code composition6.3 / 10Adequate✓ 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.

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

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

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

  • The namespaces Library.Service.Inventory.Domain ↔ Library.Service.Inventory.Domain.CommandHandlers ↔ Library.Service.Inventory.Domain.DataAccessors ↔ Library.Service.Inventory.Domain.ViewModels depend on each other. The lightest dependency in the cycle is Library.Service.Inventory.Domain → Library.Service.Inventory.Domain.CommandHandlers (Library.Service.Inventory.Domain.ImportBookInventoryCommandHandler → Library.Service.Inventory.Domain.CommandHandlers.BaseInventoryCommandHandler, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Library.Service.Inventory.Domain/CommandHandlers/ImportBookInventoryCommandHandler.cs:5

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

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.

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

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IInventoryReportDataAccessor` declares 16 members: `GetAvailableBooks`, `AddBook`, `GetBooks`, `GetBookById`, `ExistISBN`, `UpdateBookName`, `UpdateBookDescription`, `UpdateBookISBN`, `UpdateBookIssuedDate`, `UpdateBookInventoryStatus`, `AddBookInventory`, `RemoveBookInventory`, `GetBookInventoryHistories`, `DeleteBook`, `Commit`, `CommitAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Library.Service.Inventory.Domain/DataAccessors/IInventoryReportDataAccessor.cs:9

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
C1 · Data Protection0.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

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

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C2 · Access Controls0.0 / 10Critical✓ 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.

  • No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • `IdentityController.GetIdentity` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Identity/IdentityController.cs:29
  • `IdentityController.GetCustomers` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Identity/IdentityController.cs:40
  • `IdentityController.GetCustomerDetails` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Identity/IdentityController.cs:46
  • `IdentityController.GetAccount` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Identity/IdentityController.cs:52
  • `BooksController.GetAllBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:27
  • `BooksController.GetBook` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:33
  • `BooksController.UpdateBook` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:39
  • `BooksController.AddBook` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:55
  • `BooksController.GetAllAvailableBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:72
  • `BooksController.ImportBookInventory` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:78
  • `BooksController.GetBookInventoryHistories` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:91
  • `BooksController.ChangeBookInventoryStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Inventory/BooksController.cs:97
  • `CommandLogsController.GetAllCommandLogs` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/Library.Service.Logs/LogsController.cs:23, src/Library.Service.Logs/LogsController.cs:29
  • `RentalRecordsController.Rent` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Rental/RentalRecordsController.cs:28
  • `RentalRecordsController.Return` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Rental/RentalRecordsController.cs:45
  • `RentalRecordsController.GetAllUnreturnBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/Library.Service.Rental/RentalRecordsController.cs:58
  • `MonitoredCommandController.Commands` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/Library.SignalR/Controllers/TrackController.cs:17, src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs:17
  • `MonitoredCommandController.UpdateCommandStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/Library.SignalR/Controllers/TrackController.cs:24, src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs:24
  • `MonitoredCommandController.UpdateStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/Library.SignalR/Controllers/TrackController.cs:36, src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs:36
  • `AccountController.Login` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:27, REDACTED:37
  • `BookController.List` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:17
  • `BookController.Add` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:24, REDACTED:53
  • `BookController.Edit` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:30, REDACTED:38
  • `BookController._AjaxGetAvailableBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:61
  • `BookInventoryController._AjaxBulkImported` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:20
  • `BookInventoryController.Histories` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:41
  • `BookInventoryController.InStore` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:48
  • `BookInventoryController.OutStore` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:61
  • `CustomerController._AjaxGetAllCustomers` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:18
  • `LogsController.List` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:12
  • `LogsController._AjaxListItem` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:18
  • `RentalController.UnreturnedBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:16

What to do

  • Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

DM11 · Constructible invalid state8.2 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `Book`'s public constructor takes `isbn`, `bookName`, `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Library.Service.Inventory.Domain/Book.cs:19
  • `BookInventory`'s public constructor takes `notes` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `BookInventory` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/Library.Service.Inventory.Domain/BookInventory.cs:17

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain9.8 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

  • `Customer` reads `DateTime.Now` inside `ReturnBook`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Library.Service.Rental.Domain/Customer.cs:61
  • `RentBookCommandHandler` reads `DateTime.Now` inside `ExecuteCore`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Library.Service.Rental.Domain/CommandHandlers/RentBookCommandHandler.cs:18
  • `ReturnBookCommandHandler` reads `DateTime.Now` inside `ExecuteCore`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/Library.Service.Rental.Domain/CommandHandlers/ReturnBookCommandHandler.cs:18

What to do

  • Pass the instant into the domain method that needs it, or inject `TimeProvider` (BCL, .NET 8+) and read it there — then a test can choose the moment a rule is evaluated at.
DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

  • `BookRentedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Rental.Domain/Events/BookRentedEvent.cs:19
  • `BookReturnedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Rental.Domain/Events/BookReturnedEvent.cs:19
  • `RentBookRequestCreatedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Rental.Domain/Events/RentBookRequestCreatedEvent.cs:19
  • `RentBookRequestSucceedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. (×2) — src/Library.Service.Rental.Domain/Events/RentBookRequestSucceedEvent.cs:19, src/Library.Service.Inventory.Domain/Events/RentBookRequestSucceedEvent.cs:14
  • `RentBookRequestSucceedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. (×2) — src/Library.Service.Rental.Domain/Events/RentBookRequestSucceedEvent.cs:21, src/Library.Service.Inventory.Domain/Events/RentBookRequestSucceedEvent.cs:16
  • `RentBookRequestAcceptedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. (×2) — src/Library.Service.Rental.Domain/Events/RentedBookOutStoredEvent.cs:16, src/Library.Service.Inventory.Domain/Events/RentBookRequestAcceptedEvent.cs:23
  • `ReturnBookRequestCreatedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. (×2) — src/Library.Service.Rental.Domain/Events/ReturnBookRequestCreatedEvent.cs:14, src/Library.Service.Inventory.Domain/Events/ReturnBookRequestCreatedEvent.cs:19
  • `ReturnBookRequestSucceedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. (×2) — src/Library.Service.Rental.Domain/Events/ReturnBookRequestSucceedEvent.cs:19, src/Library.Service.Inventory.Domain/Events/ReturnBookRequestSucceedEvent.cs:14
  • `ReturnBookRequestSucceedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. (×2) — src/Library.Service.Rental.Domain/Events/ReturnBookRequestSucceedEvent.cs:21, src/Library.Service.Inventory.Domain/Events/ReturnBookRequestSucceedEvent.cs:16
  • `BookInventory.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Inventory.Domain/BookInventory.cs:27
  • `BookInventoryCreatedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Inventory.Domain/Events/BookInventoryCreatedEvent.cs:19
  • `BookIssuedDateChangedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Inventory.Domain/Events/BookIssuedDateChangedEvent.cs:21
  • `BookNameChangedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Inventory.Domain/Events/BookNameChangedEvent.cs:21
  • `RentBookRequestAcceptedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Inventory.Domain/Events/RentBookRequestAcceptedEvent.cs:19
  • `RentedBookOutStoredEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Service.Inventory.Domain/Events/RentedBookOutStoredEvent.cs:21
  • `DomainEvent.EventKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/Library.Domain.Core/DomainEvent.cs:20
  • `DomainEvent.AggregateId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Domain.Core/DomainEvent.cs:34
  • `DomainEvent.CommandUniqueId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Domain.Core/DomainEvent.cs:40
  • `AggregateRoot.AggregateRootId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Library.Infrastructure.EventStorage.MongoDB/EventObject.cs:13

What to do

  • Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model6.5 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `User` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Library.Service.Identity.Domain/User.cs:6
  • `Book` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Library.Service.Rental.Domain/Book.cs:6
  • `Person` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Library.Domain.Core/Entities/Person.cs:5
  • `AggregateRoot` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Library.Infrastructure.EventStorage.MongoDB/EventObject.cs:6

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state3.2 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

  • `Book` exposes publicly writable state (BookName, ISBN). — src/Library.Service.Rental.Domain/Book.cs:6
  • `Customer` exposes publicly writable state (Name). — src/Library.Service.Rental.Domain/Customer.cs:8
  • `AggregateRoot` exposes publicly writable state (Version). — src/Library.Domain.Core/AggregateRoot.cs:6
  • `Person` exposes publicly writable state (Name). — src/Library.Domain.Core/Entities/Person.cs:5
  • `AggregateRoot` exposes publicly writable state (AggregateRootId, Version, Events). — src/Library.Infrastructure.EventStorage.MongoDB/EventObject.cs:6

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary7.6 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

  • `DomainRepository` (domain layer) names `DBConcurrencyException` from `System.Data` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it. — src/Library.Domain.Core/DataAccessors/DomainRepository.cs:51

What to do

  • Invert domain→infrastructure dependencies: declare interfaces in the domain, implement them in infrastructure (Dependency Inversion).
DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

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

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

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

ED2 · Event/command shape10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.

Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.

ED3 · Event naming10.0 / 10Exemplary✓ Tool-verified

Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).

Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.

ED4 · Outbox / dual-write10.0 / 10Exemplary○ Nothing flagged

Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.

Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.

ED5 · Idempotency10.0 / 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.

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. (×2) — src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:13, src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:18

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs7.8 / 10Strong✓ Tool-verified

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

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

  • `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:13
  • `Handle` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:18
  • `Login` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:35
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×3) — src/Library.Infrastructure.InjectionFramework/InjectContainer.cs:51, src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:65, src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:69
  • A line of JavaScript has been commented out of this view's inline script rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/Library.UI/Views/Book/Add.cshtml:93

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.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.

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 a README to the 28 of 28 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

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.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
M4 · Documentation accuracy8.0 / 10Strong◐ Sampled · advisory

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

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

  • README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:2

What to do

  • Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability1.0 / 10Critical✓ 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.

  • No logging call was found in the 20 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Adopt pino (or winston) and log at meaningful points in the services you run.
  • Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

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

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

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.

PF3 · Async & latency hygiene8.5 / 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.

  • 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/Library.ApiGateway/Startup.cs:21

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Web-Security Posture0.0 / 10Critical✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • Identifier '_passwordHasher' looks like a password-hash field/property, but no KDF (PBKDF2 / Argon2 / BCrypt / PasswordHasher) was found anywhere in the source — so passwords aren't protected by a salted key-derivation function (whether a fast/plain hash, or a client-hashed value stored and compared verbatim). Password storage needs a salted KDF and a constant-time compare. — src/Library.Service.Identity/IdentityController.cs:17
  • `SecurityProtocol` explicitly selects `SecurityProtocolType.Tls`, a protocol version that is broken (SSL 2.0/3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Stop pinning versions here: leave the protocol unset (`SecurityProtocolType.SystemDefault`, or simply do not assign it) so the connection uses the OS policy and picks up TLS 1.3 and future versions without a code change. Where a version must be named explicitly, name `Tls12` and `Tls13` only. — src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:25
  • 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) — src/Library.Service.Identity/Program.cs:14, src/Library.Service.Inventory/Program.cs:14, src/Library.Service.Logs/Program.cs:14, …
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. (×4) — src/Library.Service.Identity/Program.cs:14, src/Library.Service.Inventory/Program.cs:14, src/Library.Service.Logs/Program.cs:14, …
  • No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.) — REDACTED:51

What to do

  • Store passwords with a salted KDF — `Microsoft.AspNetCore.Identity.PasswordHasher<T>`, `Rfc2898DeriveBytes` (PBKDF2), or BCrypt/Argon2 — and compare with `CryptographicOperations.FixedTimeEquals`. (A fast/plain hash, or a client-hashed value stored and compared verbatim, is not password storage.) Start in `src/Library.Service.Identity/IdentityController.cs:17`.
  • Drop SSL 2.0/3.0 and TLS 1.0/1.1 from the enabled protocol list — prefer leaving it to the OS default (`SystemDefault`) so new versions are picked up automatically, or name `Tls12`/`Tls13` explicitly if it must be pinned.
  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
  • Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
  • Set secure cookie flags — CookieSecurePolicy.Always, HttpOnly, and SameSite (Strict/Lax) on auth/session cookies. Skip only if the app sets no cookies.
X1 · Async correctness1.1 / 10Critical✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×38) — src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:28, src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:35, src/Library.Infrastructure.Messaging.SignalR/ApiRequest.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. — src/Library.ApiGateway/Startup.cs:21

What to do

  • Sync-over-async (deadlock risk) through `.Result`
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.

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.

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.

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.

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.

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.

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

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `httpContent` is a `HttpContent`, which implements `IDisposable`, and it is created here (line 118). Every use of it in `Delete` 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 httpContent = …;`), which releases it at the end of the scope on every path including a throw. — src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:118
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:31
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 64). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:64
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 98). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:98
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 116). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:116
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 137). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:137
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 153). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:153
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 179). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:179
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 198). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:198
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 226). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:226
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 255). Every use of it in `GetDataSet` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:255
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `ExecuteNoQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:28
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 60). Every use of it in `ExecuteNoQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:60
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 89). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:89
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 117). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:117
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 143). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:143
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 155). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:155
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 166). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:166
  • `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 175). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:175
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 190). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:190
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 204). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:204
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 227). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:227
  • `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 245). Every use of it in `GetDataSet` 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 da = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:245
  • `httpContent` is a `HttpContent`, which implements `IDisposable`, and it is created here (line 96). Every use of it in `Delete` 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 httpContent = …;`), which releases it at the end of the scope on every path including a throw. — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:96
  • `httpContent` is a `HttpContent`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Delete` 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 httpContent = …;`), which releases it at the end of the scope on every path including a throw. — src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:114

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

X2 · Cancellation propagation4.0 / 10Weak✓ 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 0/6 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. (×6) — src/Library.Domain.Core/BaseEventHandler.cs:30, src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/InventoryReportDataAccessor.cs:196, src/Library.Infrastructure.DataPersistence.Identity.SQLServer/IdentityReportDataAccessor.cs:128, …

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

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

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

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.

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.

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.

X24 · Document value interpolated into markup unescaped1.9 / 10Critical✓ Tool-verified

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.

  • `wrap[1]+elem+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:1031, src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6023, src/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:1031, …
  • `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×8) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:4498, src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5617, src/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:4498, …
  • `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4694, src/Library.SignalR/Scripts/jquery-1.6.4.js:4694
  • `src.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5806, src/Library.SignalR/Scripts/jquery-1.6.4.js:5806, src/Library.UI/Scripts/jquery-1.10.2.js:6318
  • `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:8577, src/Library.SignalR/Scripts/jquery-1.6.4.js:8577
  • `src.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/Library.UI/Scripts/jquery-1.10.2.js:6326
  • `elem.outerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/Library.UI/Scripts/jquery-1.10.2.js:6418
  • `wrap[1]+elem.replace(rxhtmlTag,"<$1></$2>")+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/Library.UI/Scripts/jquery-1.10.2.js:6494, src/Library.UI/Scripts/jquery-3.2.1-vsdoc.js:1107
  • `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — src/Library.UI/Scripts/jquery-3.2.1.js:1249, src/Library.UI/Scripts/jquery-3.2.1.js:1250, src/Library.UI/Scripts/jquery-3.2.1.slim.js:1250, …
  • `wrap[1]+jQuery.htmlPrefilter(elem)+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/Library.UI/Scripts/jquery-3.2.1.js:4627, src/Library.UI/Scripts/jquery-3.2.1.slim.js:4628
  • `style` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/Library.UI/Scripts/modernizr-2.6.2.js:145, src/Library.UI/Scripts/modernizr-2.8.3.js:122
  • `cssText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/Library.UI/Scripts/modernizr-2.6.2.js:1035, src/Library.UI/Scripts/modernizr-2.8.3.js:1018
  • `q` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/Library.UI/Scripts/respond.js:12, src/Library.UI/Scripts/respond.matchmedia.addListener.js:12

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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.

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.

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.

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.

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.

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

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×5) — src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:67, REDACTED:203, REDACTED:260, …

What to do

  • Swallowed exception (empty catch)
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.

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.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

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.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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.

LensScoreRatingImpact
Code Health48%Weak — gated by D2, X1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture88%StrongSolid.
Maturity51%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness15%Critical — gated by D8, D9, D13, P1, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security7%Critical — gated by D28, D29, C1, C2, S1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling57%Adequate — gated by DM2, DM5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven100%ExemplaryStrongest area.
Accessibility37%Weak — gated by AC1, AC2, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance85%StrongSolid.
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 — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 33 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.

  • AX2 Stateful singletons — no singleton implementations detected
  • 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.
  • 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
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • 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
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • X5 Nullable reference types — no NRT-eligible projects
  • 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 — 123 finding(s)
D28 · Secrets (history) · High secret · ×36
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 11 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×14
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×10
  • <select> without a programmatic label src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5419 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.SignalR/Scripts/jquery-1.6.4.js:5419 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-1.10.2.js:1601 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-1.10.2.js:5950 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.js:1250 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.js:1289 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.js:4544 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.slim.js:1251 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.slim.js:1290 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.slim.js:4545 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · Link with no accessible name · ×7
  • Link with no accessible name src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4758 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Library.SignalR/Scripts/jquery-1.6.4.js:4758 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Library.UI/Scripts/jquery-1.10.2.js:2914 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Library.UI/Scripts/jquery-3.2.1.js:1288 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Library.UI/Scripts/jquery-3.2.1.js:2689 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Library.UI/Scripts/jquery-3.2.1.slim.js:1289 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Library.UI/Scripts/jquery-3.2.1.slim.js:2690 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
D30 · Dependency Vulnerabilities · High CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×6
  • <input> without a programmatic label src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:1164 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/Library.SignalR/Scripts/jquery-1.6.4.js:1164 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/Library.UI/Scripts/jquery-1.10.2.js:2927 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/Library.UI/Scripts/jquery-1.10.2.js:3303 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.js:2702 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.slim.js:2703 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D31 · IaC & Container Security · High IaC · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×5
  • EmptyCatchBlock src/Library.Infrastructure.EventStorage.MongoDB/MongoDBEventStorage.cs:117 — 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 REDACTED:203 — 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 REDACTED:260 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Library.Infrastructure.EventStorage.SQLServer/SQLServerEventStorage.cs:97 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:67 — 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.
AC2 · Forms & labels · <textarea> without a programmatic label · ×2
  • <textarea> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.js:4706 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label src/Library.UI/Scripts/jquery-3.2.1.slim.js:4707 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D17 · Explicit Debt · WriteOnlyPrivateField · ×2
  • WriteOnlyPrivateField src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:17 — private ICommandTracker tracker — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Library.Service.Identity/IdentityController.cs:18 — private ICommandPublisher _commandPublisher — assigned 2 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title src/Library.UI/Scripts/jquery-1.10.2.js:7186 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang src/Library.UI/Views/Shared/_Layout.cshtml:4 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/Library.Service.Inventory.Domain/CommandHandlers/ImportBookInventoryCommandHandler.cs:5 — The namespaces Library.Service.Inventory.Domain ↔ Library.Service.Inventory.Domain.CommandHandlers ↔ Library.Service.Inventory.Domain.DataAccessors ↔ Library.Service.Inventory.Domain.ViewModels depend on each other. The lightest dependency in the cycle is Library.Service.Inventory.Domain → Library.Service.Inventory.Domain.CommandHandlers (Library.Service.Inventory.Domain.ImportBookInventoryCommandHandler → Library.Service.Inventory.Domain.CommandHandlers.BaseInventoryCommandHandler, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×1
  • Domain depends on infrastructure: DomainRepository src/Library.Domain.Core/DataAccessors/DomainRepository.cs:51 — `DomainRepository` (domain layer) names `DBConcurrencyException` from `System.Data` — a persistence type (in a method body). The domain should own a port and let an infrastructure adapter implement it.
S1 · Web-Security Posture · Password hashing without a KDF · ×1
  • Password hashing without a KDF src/Library.Service.Identity/IdentityController.cs:17 — Identifier '_passwordHasher' looks like a password-hash field/property, but no KDF (PBKDF2 / Argon2 / BCrypt / PasswordHasher) was found anywhere in the source — so passwords aren't protected by a salted key-derivation function (whether a fast/plain hash, or a client-hashed value stored and compared verbatim). Password storage needs a salted KDF and a constant-time compare.
Serious — 429 finding(s)
C2 · Access Controls · No authorization · ×40
  • No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • No authorization src/Library.Service.Identity/IdentityController.cs:29 — `IdentityController.GetIdentity` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Identity/IdentityController.cs:40 — `IdentityController.GetCustomers` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Identity/IdentityController.cs:46 — `IdentityController.GetCustomerDetails` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Identity/IdentityController.cs:52 — `IdentityController.GetAccount` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:27 — `BooksController.GetAllBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:33 — `BooksController.GetBook` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:39 — `BooksController.UpdateBook` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:55 — `BooksController.AddBook` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:72 — `BooksController.GetAllAvailableBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:78 — `BooksController.ImportBookInventory` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:91 — `BooksController.GetBookInventoryHistories` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Inventory/BooksController.cs:97 — `BooksController.ChangeBookInventoryStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Logs/LogsController.cs:23 — `CommandLogsController.GetAllCommandLogs` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Logs/LogsController.cs:29 — `CommandLogsController.GetAllCommandLogs` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Rental/RentalRecordsController.cs:28 — `RentalRecordsController.Rent` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Rental/RentalRecordsController.cs:45 — `RentalRecordsController.Return` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.Service.Rental/RentalRecordsController.cs:58 — `RentalRecordsController.GetAllUnreturnBooks` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.SignalR/Controllers/TrackController.cs:17 — `MonitoredCommandController.Commands` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.SignalR/Controllers/TrackController.cs:24 — `MonitoredCommandController.UpdateCommandStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.SignalR/Controllers/TrackController.cs:36 — `MonitoredCommandController.UpdateStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs:17 — `MonitoredCommandController.Commands` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs:24 — `MonitoredCommandController.UpdateCommandStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs:36 — `MonitoredCommandController.UpdateStatus` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:27 — `AccountController.Login` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • + 15 more in this group — see findings.md.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×38
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:28 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:35 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:51 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:58 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:74 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:85 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:96 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:103 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:119 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Global.asax.cs:50 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:29 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:36 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:52 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:59 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:75 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:82 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:98 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:108 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.UI/Utilities/ApiRequest.cs:115 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:28 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:35 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:51 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:58 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:74 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:81 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • + 13 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×35
  • Untrusted text written into markup unescaped src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:1031 — `wrap[1]+elem+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:4498 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4694 — `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5617 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5806 — `src.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6023 — `wrap[1]+elem+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:8577 — `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:1031 — `wrap[1]+elem+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:4498 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Scripts/jquery-1.6.4.js:4694 — `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Scripts/jquery-1.6.4.js:5617 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Scripts/jquery-1.6.4.js:5806 — `src.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Scripts/jquery-1.6.4.js:6023 — `wrap[1]+elem+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.SignalR/Scripts/jquery-1.6.4.js:8577 — `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-1.10.2.js:6094 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-1.10.2.js:6318 — `src.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-1.10.2.js:6326 — `src.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-1.10.2.js:6418 — `elem.outerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-1.10.2.js:6494 — `wrap[1]+elem.replace(rxhtmlTag,"<$1></$2>")+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-3.2.1-vsdoc.js:1107 — `wrap[1]+elem.replace(rxhtmlTag,"<$1></$2>")+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-3.2.1-vsdoc.js:4171 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-3.2.1.js:1249 — `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-3.2.1.js:1250 — `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-3.2.1.js:4627 — `wrap[1]+jQuery.htmlPrefilter(elem)+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/Library.UI/Scripts/jquery-3.2.1.js:5796 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • + 10 more in this group — see findings.md.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×25
  • Disposable created and abandoned in the method that made it src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:118 — `httpContent` is a `HttpContent`, which implements `IDisposable`, and it is created here (line 118). Every use of it in `Delete` 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 httpContent = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:31 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 31). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:64 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 64). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:98 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 98). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:116 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 116). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:137 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 137). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:153 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 153). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:179 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 179). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:198 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 198). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:226 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 226). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:255 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 255). Every use of it in `GetDataSet` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:28 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 28). Every use of it in `ExecuteNoQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:60 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 60). Every use of it in `ExecuteNoQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:89 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 89). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:117 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 117). Every use of it in `ExecuteNonQuery` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:143 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 143). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:155 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 155). Every use of it in `ExecuteScalar` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:166 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 166). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:175 — `cmd` is a `SqlCommand`, which implements `IDisposable`, and it is created here (line 175). Every use of it in `ExecuteReader` 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 cmd = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:190 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 190). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:204 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 204). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:227 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 227). Every use of it in `ExecuteDataTable` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it REDACTED:245 — `da` is a `SqlDataAdapter`, which implements `IDisposable`, and it is created here (line 245). Every use of it in `GetDataSet` 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 da = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:96 — `httpContent` is a `HttpContent`, which implements `IDisposable`, and it is created here (line 96). Every use of it in `Delete` 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 httpContent = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:114 — `httpContent` is a `HttpContent`, which implements `IDisposable`, and it is created here (line 114). Every use of it in `Delete` 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 httpContent = …;`), which releases it at the end of the scope on every path including a throw.
D31 · IaC & Container Security · Medium IaC · ×17
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×10
  • FileTooLong: Scripts/jquery-1.10.2.js src/Library.UI/Scripts/jquery-1.10.2.js — FileTooLong — 5026 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4526 over it, 10.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Scripts/jquery-3.2.1.js src/Library.UI/Scripts/jquery-3.2.1.js — FileTooLong — 5000 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4500 over it, 10.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Scripts/jquery-1.6.4.js src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js — FileTooLong — 4656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4156 over it, 9.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Scripts/jquery-1.6.4.js src/Library.SignalR/Scripts/jquery-1.6.4.js — FileTooLong — 4656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4156 over it, 9.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Scripts/jquery-3.2.1.slim.js src/Library.UI/Scripts/jquery-3.2.1.slim.js — FileTooLong — 3952 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3452 over it, 7.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Scripts/jquery.signalR-2.2.2.js src/Library.SignalR/Library.SignalR/Scripts/jquery.signalR-2.2.2.js — FileTooLong — 1580 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1080 over it, 3.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Scripts/jquery.signalR-2.2.2.js src/Library.SignalR/Scripts/jquery.signalR-2.2.2.js — FileTooLong — 1580 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1080 over it, 3.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Scripts/bootstrap.js src/Library.UI/Scripts/bootstrap.js — FileTooLong — 1344 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 844 over it, 2.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 391 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 209 over it, 1.42× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×8
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:3518 — `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:3573 — `.dropdown-menu > .active > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:3592 — `.open > a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:3717 — `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:4307 — `.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:5879 — `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:5913 — `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Library.UI/Content/bootstrap.css:6354 — `.carousel-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×6
  • Animation without a prefers-reduced-motion guard src/Library.UI/Content/bootstrap.css:3500 — `.collapsing` moves (`transition-property: height, visibility`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Library.UI/Content/bootstrap.css:5148 — `.progress-bar` moves (`transition: width .6s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Library.UI/Content/bootstrap.css:5162 — `.progress.active .progress-bar` moves (`animation: progress-bar-stripes 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Library.UI/Content/bootstrap.css:5884 — `.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Library.UI/Content/bootstrap.css:6250 — `.carousel-inner > .item` moves (`transition: .6s ease-in-out left`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Library.UI/Content/bootstrap.css:6260 — `.carousel-inner > .item` moves (`transition: transform .6s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
X2 · Cancellation propagation · Async method without CancellationToken · ×6
  • Async method without CancellationToken: HandleAsync src/Library.Domain.Core/BaseEventHandler.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CommitAsync src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/InventoryReportDataAccessor.cs:196 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CommitAsync src/Library.Infrastructure.DataPersistence.Identity.SQLServer/IdentityReportDataAccessor.cs:128 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CommitAsync src/Library.Infrastructure.DataPersistence.Rental.SQLServer/RentalReportDataAccessor.cs:35 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Login REDACTED:37 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GenerateUserIdentityAsync src/Library.UI/Models/IdentityModels.cs:11 — No CancellationToken parameter — this work can't be stopped early once started.
AC3 · Page structure · Data table has no header cells · ×5
  • Data table has no header cells src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:1325 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:8573 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells src/Library.SignalR/Scripts/jquery-1.6.4.js:1325 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells src/Library.SignalR/Scripts/jquery-1.6.4.js:8573 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells src/Library.UI/Scripts/jquery-1.10.2.js:3466 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×5
  • Duplicated block (17 lines × 2) REDACTED:83 — REDACTED:83-99 | REDACTED:25-41 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 2) REDACTED:111 — REDACTED:111-127 | REDACTED:58-74 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (17 lines × 2) src/Library.Domain.Core/Models/CommandLogModel.cs:7 — src/Library.Domain.Core/Models/CommandLogModel.cs:7-23 | src/Library.UI/ViewModels/LogItemViewModel.cs:7-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (17 lines × 2) REDACTED:31 — REDACTED:31-47 | REDACTED:63-79 — 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 `REDACTED:31` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Library.Service.Rental.Domain/ViewModels/UnreturnedBookViewModel.cs:5 — src/Library.Service.Rental.Domain/ViewModels/UnreturnedBookViewModel.cs:5-21 | src/Library.UI/ViewModels/UnreturnedBookViewModel.cs:5-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Library.Service.Rental.Domain/ViewModels/UnreturnedBookViewModel.cs:5` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
DM5 · Encapsulated state · Mutable entity · ×5
  • Mutable entity: Book src/Library.Service.Rental.Domain/Book.cs:6 — `Book` exposes publicly writable state (BookName, ISBN).
  • Mutable entity: Customer src/Library.Service.Rental.Domain/Customer.cs:8 — `Customer` exposes publicly writable state (Name).
  • Mutable entity: AggregateRoot src/Library.Domain.Core/AggregateRoot.cs:6 — `AggregateRoot` exposes publicly writable state (Version).
  • Mutable entity: Person src/Library.Domain.Core/Entities/Person.cs:5 — `Person` exposes publicly writable state (Name).
  • Mutable entity: AggregateRoot src/Library.Infrastructure.EventStorage.MongoDB/EventObject.cs:6 — `AggregateRoot` exposes publicly writable state (AggregateRootId, Version, Events).
X3 · Exception handling · Swallowed exception (empty catch) · ×5
  • Swallowed exception (empty catch) src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:67 — 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) REDACTED:203 — 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) REDACTED:260 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Library.Infrastructure.EventStorage.SQLServer/SQLServerEventStorage.cs:97 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/Library.Infrastructure.EventStorage.MongoDB/MongoDBEventStorage.cs:117 — 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.
DM4 · Rich vs anemic model · Anemic entity · ×4
  • Anemic entity: User src/Library.Service.Identity.Domain/User.cs:6 — `User` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Book src/Library.Service.Rental.Domain/Book.cs:6 — `Book` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: Person src/Library.Domain.Core/Entities/Person.cs:5 — `Person` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AggregateRoot src/Library.Infrastructure.EventStorage.MongoDB/EventObject.cs:6 — `AggregateRoot` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
AC2 · Forms & labels · <fieldset> without a <legend> · ×3
  • <fieldset> without a <legend> src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5420 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> src/Library.SignalR/Scripts/jquery-1.6.4.js:5420 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> src/Library.UI/Scripts/jquery-1.10.2.js:5951 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×3
  • Heading level jumps from h2 to h4 src/Library.UI/Views/Account/ForgotPassword.cshtml:11 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h4 src/Library.UI/Views/Account/Register.cshtml:11 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h4 src/Library.UI/Views/Account/ResetPassword.cshtml:11 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×3
  • Duplicated block (19 lines × 4) src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:23 — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:23-41 | src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:23-41 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:23-41 | src/Library.UI/Utilities/ApiRequest.cs:24-42 — before extracting anything, compare `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs` and `src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 4) src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:45 — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:45-63 | src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:45-63 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:45-63 | src/Library.UI/Utilities/ApiRequest.cs:46-64 — before extracting anything, compare `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs` and `src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (19 lines × 4) src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:68 — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:68-86 | src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:90-108 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:68-86 | src/Library.UI/Utilities/ApiRequest.cs:69-87 — before extracting anything, compare `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs` and `src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/Extensions/ConvertExtension.cs:23 — src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/Extensions/ConvertExtension.cs:23-31 | src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/Extensions/ConvertExtension.cs:61-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 `src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/Extensions/ConvertExtension.cs:23` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) REDACTED:139 — REDACTED:139-147 | REDACTED:94-102 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) src/Library.SignalR/Hubs/CommandHub.cs:44 — src/Library.SignalR/Hubs/CommandHub.cs:44-52 | src/Library.SignalR/Library.SignalR/Hubs/CommandHub.cs:44-52 — before extracting anything, compare `src/Library.SignalR/Hubs/CommandHub.cs` and `src/Library.SignalR/Library.SignalR/Hubs/CommandHub.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D5 · Coupling · Off the main sequence · ×3
  • Off the main sequence: Library.Infrastructure.InjectionFramework src/Library.Infrastructure.InjectionFramework/Library.Infrastructure.InjectionFramework.csproj:1 — Library.Infrastructure.InjectionFramework: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
  • Off the main sequence: Library.Infrastructure.DataPersistence.Core.SQLServer src/Library.Infrastructure.DataPersistence.Core.SQLServer/Library.Infrastructure.DataPersistence.Core.SQLServer.csproj:1 — Library.Infrastructure.DataPersistence.Core.SQLServer: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
  • Off the main sequence: Library.Infrastructure.Core src/Library.Infrastructure.Core/Library.Infrastructure.Core.csproj:1 — Library.Infrastructure.Core: abstractness 0.00, instability 0.09, distance 0.91 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
DM12 · Ambient inputs in the domain · Domain type reads the wall clock · ×3
  • Domain type reads the wall clock: Customer src/Library.Service.Rental.Domain/Customer.cs:61 — `Customer` reads `DateTime.Now` inside `ReturnBook`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: RentBookCommandHandler src/Library.Service.Rental.Domain/CommandHandlers/RentBookCommandHandler.cs:18 — `RentBookCommandHandler` reads `DateTime.Now` inside `ExecuteCore`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
  • Domain type reads the wall clock: ReturnBookCommandHandler src/Library.Service.Rental.Domain/CommandHandlers/ReturnBookCommandHandler.cs:18 — `ReturnBookCommandHandler` reads `DateTime.Now` inside `ExecuteCore`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
AC3 · Page structure · Page without a main landmark · ×2
  • Page without a main landmark REDACTED:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark src/Library.UI/Views/Shared/_Layout.cshtml:4 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D1 · Cyclomatic Complexity · jquery-1.6.4.Sizzle (cyclomatic 51) · ×2
  • jquery-1.6.4.Sizzle (cyclomatic 51) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3715 — jquery-1.6.4.Sizzle has cyclomatic complexity 51 (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.
  • jquery-1.6.4.Sizzle (cyclomatic 51) src/Library.SignalR/Scripts/jquery-1.6.4.js:3715 — jquery-1.6.4.Sizzle has cyclomatic complexity 51 (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 · jquery-1.6.4.liveHandler (cyclomatic 29) · ×2
  • jquery-1.6.4.liveHandler (cyclomatic 29) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3580 — jquery-1.6.4.liveHandler has cyclomatic complexity 29 (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.
  • jquery-1.6.4.liveHandler (cyclomatic 29) src/Library.SignalR/Scripts/jquery-1.6.4.js:3580 — jquery-1.6.4.liveHandler has cyclomatic complexity 29 (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 · jquery-1.6.4.Sizzle.filter (cyclomatic 25) · ×2
  • jquery-1.6.4.Sizzle.filter (cyclomatic 25) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3914 — jquery-1.6.4.Sizzle.filter has cyclomatic complexity 25 (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.
  • jquery-1.6.4.Sizzle.filter (cyclomatic 25) src/Library.SignalR/Scripts/jquery-1.6.4.js:3914 — jquery-1.6.4.Sizzle.filter has cyclomatic complexity 25 (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 · jquery-1.6.4.ajaxConvert (cyclomatic 21) · ×2
  • jquery-1.6.4.ajaxConvert (cyclomatic 21) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7423 — jquery-1.6.4.ajaxConvert has cyclomatic complexity 21 (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.
  • jquery-1.6.4.ajaxConvert (cyclomatic 21) src/Library.SignalR/Scripts/jquery-1.6.4.js:7423 — jquery-1.6.4.ajaxConvert has cyclomatic complexity 21 (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 · jquery-1.6.4.getWH (cyclomatic 20) · ×2
  • jquery-1.6.4.getWH (cyclomatic 20) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6473 — jquery-1.6.4.getWH has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 2 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. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
  • jquery-1.6.4.getWH (cyclomatic 20) src/Library.SignalR/Scripts/jquery-1.6.4.js:6473 — jquery-1.6.4.getWH has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 2 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. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · jquery-1.6.4.jQuery.buildFragment (cyclomatic 18) · ×2
  • jquery-1.6.4.jQuery.buildFragment (cyclomatic 18) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5837 — jquery-1.6.4.jQuery.buildFragment has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
  • jquery-1.6.4.jQuery.buildFragment (cyclomatic 18) src/Library.SignalR/Scripts/jquery-1.6.4.js:5837 — jquery-1.6.4.jQuery.buildFragment has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · jquery-1.6.4.ajaxHandleResponses (cyclomatic 18) · ×2
  • jquery-1.6.4.ajaxHandleResponses (cyclomatic 18) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7359 — jquery-1.6.4.ajaxHandleResponses 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. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
  • jquery-1.6.4.ajaxHandleResponses (cyclomatic 18) src/Library.SignalR/Scripts/jquery-1.6.4.js:7359 — jquery-1.6.4.ajaxHandleResponses 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. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 16) · ×2
  • jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 16) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7516 — jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 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. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
  • jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 16) src/Library.SignalR/Scripts/jquery-1.6.4.js:7516 — jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 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. This is NOT this file's highest cyclomatic complexity: jquery-1.6.4.jQuery.each() (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D2 · Cognitive Complexity · jquery-1.6.4.Sizzle.filter (cognitive 80) · ×2
  • jquery-1.6.4.Sizzle.filter (cognitive 80) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3914 — jquery-1.6.4.Sizzle.filter has cognitive complexity 80 (threshold 15). Drivers by points: if/else 18 (68 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 55). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • jquery-1.6.4.Sizzle.filter (cognitive 80) src/Library.SignalR/Scripts/jquery-1.6.4.js:3914 — jquery-1.6.4.Sizzle.filter has cognitive complexity 80 (threshold 15). Drivers by points: if/else 18 (68 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 55). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.6.4.Sizzle (cognitive 79) · ×2
  • jquery-1.6.4.Sizzle (cognitive 79) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3715 — jquery-1.6.4.Sizzle has cognitive complexity 79 (threshold 15). Drivers by points: if/else 27 (51 pts), boolean chains 15, loops 5 (13 pts) (nesting depth added 32). 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.
  • jquery-1.6.4.Sizzle (cognitive 79) src/Library.SignalR/Scripts/jquery-1.6.4.js:3715 — jquery-1.6.4.Sizzle has cognitive complexity 79 (threshold 15). Drivers by points: if/else 27 (51 pts), boolean chains 15, loops 5 (13 pts) (nesting depth added 32). 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 · jquery-1.6.4.ajaxConvert (cognitive 50) · ×2
  • jquery-1.6.4.ajaxConvert (cognitive 50) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7423 — jquery-1.6.4.ajaxConvert has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (38 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • jquery-1.6.4.ajaxConvert (cognitive 50) src/Library.SignalR/Scripts/jquery-1.6.4.js:7423 — jquery-1.6.4.ajaxConvert has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (38 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 31). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.6.4.liveHandler (cognitive 45) · ×2
  • jquery-1.6.4.liveHandler (cognitive 45) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3580 — jquery-1.6.4.liveHandler has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 9, loops 4 (5 pts) (nesting depth added 20). 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.
  • jquery-1.6.4.liveHandler (cognitive 45) src/Library.SignalR/Scripts/jquery-1.6.4.js:3580 — jquery-1.6.4.liveHandler has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 9, loops 4 (5 pts) (nesting depth added 20). 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 · jquery-1.6.4.dirCheck (cognitive 31) · ×2
  • jquery-1.6.4.dirCheck (cognitive 31) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4982 — jquery-1.6.4.dirCheck has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (27 pts), loops 2 (4 pts) (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • jquery-1.6.4.dirCheck (cognitive 31) src/Library.SignalR/Scripts/jquery-1.6.4.js:4982 — jquery-1.6.4.dirCheck has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (27 pts), loops 2 (4 pts) (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.6.4.ajaxHandleResponses (cognitive 29) · ×2
  • jquery-1.6.4.ajaxHandleResponses (cognitive 29) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7359 — jquery-1.6.4.ajaxHandleResponses has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (6 pts), boolean chains 4 (nesting depth added 11). 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.
  • jquery-1.6.4.ajaxHandleResponses (cognitive 29) src/Library.SignalR/Scripts/jquery-1.6.4.js:7359 — jquery-1.6.4.ajaxHandleResponses has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (6 pts), boolean chains 4 (nesting depth added 11). 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 · jquery-1.6.4.getWH (cognitive 27) · ×2
  • jquery-1.6.4.getWH (cognitive 27) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6473 — jquery-1.6.4.getWH has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 9, ternaries 2 (nesting depth added 7). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 6480, 6505). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
  • jquery-1.6.4.getWH (cognitive 27) src/Library.SignalR/Scripts/jquery-1.6.4.js:6473 — jquery-1.6.4.getWH has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 9, ternaries 2 (nesting depth added 7). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 6480, 6505). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") (cognitive 22) · ×2
  • jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") (cognitive 22) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7516 — jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 6 (nesting depth added 10). Of this number, 19 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") (cognitive 22) src/Library.SignalR/Scripts/jquery-1.6.4.js:7516 — jquery-1.6.4.jQuery.ajaxPrefilter("json jsonp") has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 6 (nesting depth added 10). Of this number, 19 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.6.4.dirNodeCheck (cognitive 19) · ×2
  • jquery-1.6.4.dirNodeCheck (cognitive 19) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4949 — jquery-1.6.4.dirNodeCheck has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 12). 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.
  • jquery-1.6.4.dirNodeCheck (cognitive 19) src/Library.SignalR/Scripts/jquery-1.6.4.js:4949 — jquery-1.6.4.dirNodeCheck has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 12). 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 · jquery-1.6.4.inspectPrefiltersOrTransports (cognitive 16) · ×2
  • jquery-1.6.4.inspectPrefiltersOrTransports (cognitive 16) src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6629 — jquery-1.6.4.inspectPrefiltersOrTransports has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (7 pts), loops 1, ternaries 1 (nesting depth added 3). 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.
  • jquery-1.6.4.inspectPrefiltersOrTransports (cognitive 16) src/Library.SignalR/Scripts/jquery-1.6.4.js:6629 — jquery-1.6.4.inspectPrefiltersOrTransports has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (7 pts), loops 1, ternaries 1 (nesting depth added 3). 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.
D3 · God Classes · FunctionTooLong · ×2
  • FunctionTooLong: respond.getEmValue src/Library.UI/Scripts/respond.js:72 — FunctionTooLong — getEmValue runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: respond.matchmedia.addListener.getEmValue src/Library.UI/Scripts/respond.matchmedia.addListener.js:121 — FunctionTooLong — getEmValue runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) REDACTED:235 — REDACTED:235-249 | REDACTED:245-259 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:235` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/Library.UI/Models/AccountViewModels.cs:64 — src/Library.UI/Models/AccountViewModels.cs:64-78 | src/Library.UI/Models/AccountViewModels.cs:83-97 — 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 (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) REDACTED:151 — REDACTED:151-160 | REDACTED:112-121 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) src/Library.UI/Models/ManageViewModels.cs:30 — src/Library.UI/Models/ManageViewModels.cs:30-39 | src/Library.UI/Models/ManageViewModels.cs:49-58 — 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 lines × 2) · ×2
  • Duplicated block (36 lines × 2) src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs:15 — src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs:15-160 | src/Library.Service.Identity/AppsettingDBConnectionStringProvider.cs:12-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs:15` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (36 lines × 2) src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs:15 — src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs:15-160 | src/Library.Service.Rental/AppsettingDBConnectionStringProvider.cs:12-47 — `src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs` and `src/Library.Service.Rental/AppsettingDBConnectionStringProvider.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 146 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs:15` 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. 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 (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) REDACTED:164 — REDACTED:164-169 | REDACTED:135-140 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) src/Library.SignalR/Hubs/CommandHub.cs:35 — src/Library.SignalR/Hubs/CommandHub.cs:35-40 | src/Library.SignalR/Library.SignalR/Hubs/CommandHub.cs:35-40 — before extracting anything, compare `src/Library.SignalR/Hubs/CommandHub.cs` and `src/Library.SignalR/Library.SignalR/Hubs/CommandHub.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
DM11 · Constructible invalid state · Constructible in an invalid state · ×2
  • Constructible in an invalid state: Book src/Library.Service.Inventory.Domain/Book.cs:19 — `Book`'s public constructor takes `isbn`, `bookName`, `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Book` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: BookInventory src/Library.Service.Inventory.Domain/BookInventory.cs:17 — `BookInventory`'s public constructor takes `notes` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `BookInventory` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
GD1 · Unfinished & placeholder code · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:13 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:18 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:13 — `HandleAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/Library.Service.Identity.Domain/EventHandlers/AdministratorCreatedEventHandler.cs:18 — `Handle` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×2
  • Sync-over-async blocking — 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/Library.ApiGateway/Startup.cs:21 — `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
AC1 · Text alternatives · <object> without a text alternative · ×1
  • <object> without a text alternative src/Library.UI/Scripts/jquery-1.10.2.js:5953 — A <object> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.5 · ×1
  • Low contrast colour pair in CSS (2.5:1) src/Library.UI/Content/bootstrap.css:3173 — `.btn-success` sets color: #fff on background-color: #5cb85c — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 33 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D1 · Cyclomatic Complexity · jquery-3.2.1.defaultPrefilter (cyclomatic 45) · ×1
  • jquery-3.2.1.defaultPrefilter (cyclomatic 45) src/Library.UI/Scripts/jquery-3.2.1.js:6587 — jquery-3.2.1.defaultPrefilter has cyclomatic complexity 45 (threshold 15). Of this number, 41 points are the body's own statements and 4 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 · jquery-1.10.2.Sizzle (cyclomatic 39) · ×1
  • jquery-1.10.2.Sizzle (cyclomatic 39) src/Library.UI/Scripts/jquery-1.10.2.js:1184 — jquery-1.10.2.Sizzle has cyclomatic complexity 39 (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 · jquery-1.10.2.jQuery.Callbacks (cyclomatic 37) · ×1
  • jquery-1.10.2.jQuery.Callbacks (cyclomatic 37) src/Library.UI/Scripts/jquery-1.10.2.js:2995 — jquery-1.10.2.jQuery.Callbacks has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 4 of the 37 points are its own statements and the rest belongs to 8 function items inside it that branch (fire, a function literal at line 3053, a function literal at line 3132, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · jquery-1.10.2.defaultPrefilter (cyclomatic 34) · ×1
  • jquery-1.10.2.defaultPrefilter (cyclomatic 34) src/Library.UI/Scripts/jquery-1.10.2.js:8932 — jquery-1.10.2.defaultPrefilter has cyclomatic complexity 34 (threshold 15). Of this number, 31 points are the body's own statements and 3 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 · jquery-1.10.2.matcherFromGroupMatchers · ×1
  • jquery-1.10.2.matcherFromGroupMatchers::superMatcher (cyclomatic 33) src/Library.UI/Scripts/jquery-1.10.2.js:2699 — jquery-1.10.2.matcherFromGroupMatchers::superMatcher has cyclomatic complexity 33 (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 · jquery-1.10.2.setMatcher (cyclomatic 32) · ×1
  • jquery-1.10.2.setMatcher (cyclomatic 32) src/Library.UI/Scripts/jquery-1.10.2.js:2547 — jquery-1.10.2.setMatcher has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to one function literal inside it that branches (line 2554). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · jquery-3.2.1.jQuery.Callbacks (cyclomatic 31) · ×1
  • jquery-3.2.1.jQuery.Callbacks (cyclomatic 31) src/Library.UI/Scripts/jquery-3.2.1.js:3186 — jquery-3.2.1.jQuery.Callbacks has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (fire, a function literal at line 3267, a function literal at line 3258, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · jquery-3.2.1.slim.jQuery.Callbacks (cyclomatic 31) · ×1
  • jquery-3.2.1.slim.jQuery.Callbacks (cyclomatic 31) src/Library.UI/Scripts/jquery-3.2.1.slim.js:3187 — jquery-3.2.1.slim.jQuery.Callbacks has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (fire, a function literal at line 3268, a function literal at line 3259, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · respond.applyMedia (cyclomatic 30) · ×1
  • respond.applyMedia (cyclomatic 30) src/Library.UI/Scripts/respond.js:97 — respond.applyMedia has cyclomatic complexity 30 (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 · respond.matchmedia.addListener.applyMedia (cyclomatic 30) · ×1
  • respond.matchmedia.addListener.applyMedia (cyclomatic 30) src/Library.UI/Scripts/respond.matchmedia.addListener.js:146 — respond.matchmedia.addListener.applyMedia has cyclomatic complexity 30 (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 · jquery-3.2.1.jQuery.ajaxTransport() (cyclomatic 27) · ×1
  • jquery-3.2.1.jQuery.ajaxTransport() (cyclomatic 27) src/Library.UI/Scripts/jquery-3.2.1.js:9085 — jquery-3.2.1.jQuery.ajaxTransport() has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 9091, 9131, 9181, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · jquery-1.10.2.ajaxConvert (cyclomatic 25) · ×1
  • jquery-1.10.2.ajaxConvert (cyclomatic 25) src/Library.UI/Scripts/jquery-1.10.2.js:8242 — jquery-1.10.2.ajaxConvert has cyclomatic complexity 25 (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 · jquery-3.2.1.ajaxConvert (cyclomatic 25) · ×1
  • jquery-3.2.1.ajaxConvert (cyclomatic 25) src/Library.UI/Scripts/jquery-3.2.1.js:8342 — jquery-3.2.1.ajaxConvert has cyclomatic complexity 25 (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 · jquery-1.10.2.internalData (cyclomatic 24) · ×1
  • jquery-1.10.2.internalData (cyclomatic 24) src/Library.UI/Scripts/jquery-1.10.2.js:3545 — jquery-1.10.2.internalData has cyclomatic complexity 24 (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 · bootstrap.Tooltip.show (cyclomatic 22) · ×1
  • bootstrap.Tooltip.show (cyclomatic 22) src/Library.UI/Scripts/bootstrap.js:1395 — bootstrap.Tooltip.show has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function item 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.
D1 · Cyclomatic Complexity · jquery-3.2.1.adjustCSS (cyclomatic 22) · ×1
  • jquery-3.2.1.adjustCSS (cyclomatic 22) src/Library.UI/Scripts/jquery-3.2.1.js:4382 — jquery-3.2.1.adjustCSS has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · jquery-3.2.1.domManip (cyclomatic 22) · ×1
  • jquery-3.2.1.domManip (cyclomatic 22) src/Library.UI/Scripts/jquery-3.2.1.js:5506 — jquery-3.2.1.domManip has cyclomatic complexity 22 (threshold 15). Of this number, 21 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.
D1 · Cyclomatic Complexity · jquery-3.2.1.slim.adjustCSS (cyclomatic 22) · ×1
  • jquery-3.2.1.slim.adjustCSS (cyclomatic 22) src/Library.UI/Scripts/jquery-3.2.1.slim.js:4383 — jquery-3.2.1.slim.adjustCSS has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · jquery-3.2.1.slim.domManip (cyclomatic 22) · ×1
  • jquery-3.2.1.slim.domManip (cyclomatic 22) src/Library.UI/Scripts/jquery-3.2.1.slim.js:5507 — jquery-3.2.1.slim.domManip has cyclomatic complexity 22 (threshold 15). Of this number, 21 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.
D1 · Cyclomatic Complexity · jquery-1.10.2.addCombinator (cyclomatic 21) · ×1
  • jquery-1.10.2.addCombinator (cyclomatic 21) src/Library.UI/Scripts/jquery-1.10.2.js:2462 — jquery-1.10.2.addCombinator has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2478, 2469). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · jquery-1.10.2.select (cyclomatic 20) · ×1
  • jquery-1.10.2.select (cyclomatic 20) src/Library.UI/Scripts/jquery-1.10.2.js:2830 — jquery-1.10.2.select has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-1.10.2.showHide (cyclomatic 20) · ×1
  • jquery-1.10.2.showHide (cyclomatic 20) src/Library.UI/Scripts/jquery-1.10.2.js:6762 — jquery-1.10.2.showHide has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-3.2.1.buildFragment (cyclomatic 20) · ×1
  • jquery-3.2.1.buildFragment (cyclomatic 20) src/Library.UI/Scripts/jquery-3.2.1.js:4599 — jquery-3.2.1.buildFragment has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-3.2.1.slim.buildFragment (cyclomatic 20) · ×1
  • jquery-3.2.1.slim.buildFragment (cyclomatic 20) src/Library.UI/Scripts/jquery-3.2.1.slim.js:4600 — jquery-3.2.1.slim.buildFragment has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-1.10.2.internalRemoveData (cyclomatic 19) · ×1
  • jquery-1.10.2.internalRemoveData (cyclomatic 19) src/Library.UI/Scripts/jquery-1.10.2.js:3632 — jquery-1.10.2.internalRemoveData has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BaseEventHandler.AddEventLog (cyclomatic 18) · ×1
  • BaseEventHandler.AddEventLog (cyclomatic 18) src/Library.Domain.Core/BaseEventHandler.cs:38 — BaseEventHandler.AddEventLog has cyclomatic complexity 18 (threshold 15). Of this number, 17 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.
D1 · Cyclomatic Complexity · jquery-1.10.2.matcherFromTokens (cyclomatic 18) · ×1
  • jquery-1.10.2.matcherFromTokens (cyclomatic 18) src/Library.UI/Scripts/jquery-1.10.2.js:2639 — jquery-1.10.2.matcherFromTokens has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong 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.
D1 · Cyclomatic Complexity · jquery-1.10.2.fixCloneNodeIssues (cyclomatic 18) · ×1
  • jquery-1.10.2.fixCloneNodeIssues (cyclomatic 18) src/Library.UI/Scripts/jquery-1.10.2.js:6287 — jquery-1.10.2.fixCloneNodeIssues has cyclomatic complexity 18 (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 · jquery-1.10.2.jQuery.speed (cyclomatic 18) · ×1
  • jquery-1.10.2.jQuery.speed (cyclomatic 18) src/Library.UI/Scripts/jquery-1.10.2.js:9311 — jquery-1.10.2.jQuery.speed has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · jquery-3.2.1.Animation (cyclomatic 18) · ×1
  • jquery-3.2.1.Animation (cyclomatic 18) src/Library.UI/Scripts/jquery-3.2.1.js:6788 — jquery-3.2.1.Animation has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (tick, a function literal at line 6849, a function literal at line 6843). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · jquery-3.2.1.jQuery.speed (cyclomatic 18) · ×1
  • jquery-3.2.1.jQuery.speed (cyclomatic 18) src/Library.UI/Scripts/jquery-3.2.1.js:6951 — jquery-3.2.1.jQuery.speed has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong 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.
D1 · Cyclomatic Complexity · jquery-3.2.1.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 18) · ×1
  • jquery-3.2.1.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 18) src/Library.UI/Scripts/jquery-3.2.1.js:9301 — jquery-3.2.1.jQuery.ajaxPrefilter("json jsonp") has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 2 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 · bootstrap.Modal.backdrop (cyclomatic 17) · ×1
  • bootstrap.Modal.backdrop (cyclomatic 17) src/Library.UI/Scripts/bootstrap.js:1074 — bootstrap.Modal.backdrop has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 2 function items 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 · jquery-1.10.2.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 17) · ×1
  • jquery-1.10.2.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 17) src/Library.UI/Scripts/jquery-1.10.2.js:8419 — jquery-1.10.2.jQuery.ajaxPrefilter("json jsonp") has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 2 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 · respond.translate (cyclomatic 17) · ×1
  • respond.translate (cyclomatic 17) src/Library.UI/Scripts/respond.js:145 — respond.translate has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · respond.matchmedia.addListener.translate (cyclomatic 17) · ×1
  • respond.matchmedia.addListener.translate (cyclomatic 17) src/Library.UI/Scripts/respond.matchmedia.addListener.js:194 — respond.matchmedia.addListener.translate has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · jquery-1.10.2.tokenize (cyclomatic 16) · ×1
  • jquery-1.10.2.tokenize (cyclomatic 16) src/Library.UI/Scripts/jquery-1.10.2.js:2386 — jquery-1.10.2.tokenize has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-1.10.2.ajaxHandleResponses (cyclomatic 16) · ×1
  • jquery-1.10.2.ajaxHandleResponses (cyclomatic 16) src/Library.UI/Scripts/jquery-1.10.2.js:8187 — jquery-1.10.2.ajaxHandleResponses has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-1.10.2.Animation (cyclomatic 16) · ×1
  • jquery-1.10.2.Animation (cyclomatic 16) src/Library.UI/Scripts/jquery-1.10.2.js:8762 — jquery-1.10.2.Animation has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (tick, a function literal at line 8811, a function literal at line 8805). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · jquery-3.2.1.ajaxHandleResponses (cyclomatic 16) · ×1
  • jquery-3.2.1.ajaxHandleResponses (cyclomatic 16) src/Library.UI/Scripts/jquery-3.2.1.js:8286 — jquery-3.2.1.ajaxHandleResponses has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: src/Library.UI/Scripts/respond.js src/Library.UI/Scripts/respond.js:97 — src/Library.UI/Scripts/respond.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in respond.applyMedia at line 97. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2017-11-09..2018-02-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2017-11-09 18:50:34 -08:00' --until='2018-02-07 18:50:34 -08:00' --full-history --no-merges -- src/Library.UI/Scripts/respond.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · jquery-3.2.1.defaultPrefilter (cognitive 81) · ×1
  • jquery-3.2.1.defaultPrefilter (cognitive 81) src/Library.UI/Scripts/jquery-3.2.1.js:6587 — jquery-3.2.1.defaultPrefilter has cognitive complexity 81 (threshold 15). Drivers by points: if/else 27 (64 pts), boolean chains 12, loops 3 (5 pts) (nesting depth added 39). Of this number, 73 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.10.2.Sizzle (cognitive 73) · ×1
  • jquery-1.10.2.Sizzle (cognitive 73) src/Library.UI/Scripts/jquery-1.10.2.js:1184 — jquery-1.10.2.Sizzle has cognitive complexity 73 (threshold 15). Drivers by points: if/else 20 (50 pts), boolean chains 15, error handling 1 (4 pts), loops 1 (4 pts) (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.10.2.ajaxConvert (cognitive 73) · ×1
  • jquery-1.10.2.ajaxConvert (cognitive 73) src/Library.UI/Scripts/jquery-1.10.2.js:8242 — jquery-1.10.2.ajaxConvert has cognitive complexity 73 (threshold 15). Drivers by points: if/else 14 (47 pts), loops 3 (8 pts), ternaries 1 (7 pts), error handling 1 (6 pts), boolean chains 5 (nesting depth added 49). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-3.2.1.ajaxConvert (cognitive 73) · ×1
  • jquery-3.2.1.ajaxConvert (cognitive 73) src/Library.UI/Scripts/jquery-3.2.1.js:8342 — jquery-3.2.1.ajaxConvert has cognitive complexity 73 (threshold 15). Drivers by points: if/else 14 (47 pts), loops 3 (8 pts), ternaries 1 (7 pts), error handling 1 (6 pts), boolean chains 5 (nesting depth added 49). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.10.2.addCombinator (cognitive 54) · ×1
  • jquery-1.10.2.addCombinator (cognitive 54) src/Library.UI/Scripts/jquery-1.10.2.js:2462 — jquery-1.10.2.addCombinator has cognitive complexity 54 (threshold 15). Drivers by points: if/else 10 (37 pts), boolean chains 8, loops 3 (8 pts), ternaries 1 (nesting depth added 32). Most of this is not in the body itself: 2 of the 54 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2478, 2469). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · jquery-1.10.2.matcherFromGroupMatchers · ×1
  • jquery-1.10.2.matcherFromGroupMatchers::superMatcher (cognitive 54) src/Library.UI/Scripts/jquery-1.10.2.js:2699 — jquery-1.10.2.matcherFromGroupMatchers::superMatcher has cognitive complexity 54 (threshold 15). Drivers by points: if/else 13 (32 pts), boolean chains 12, loops 4 (10 pts) (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.10.2.jQuery.Callbacks (cognitive 53) · ×1
  • jquery-1.10.2.jQuery.Callbacks (cognitive 53) src/Library.UI/Scripts/jquery-1.10.2.js:2995 — jquery-1.10.2.jQuery.Callbacks has cognitive complexity 53 (threshold 15). Drivers by points: if/else 20 (37 pts), boolean chains 12, loops 2 (3 pts), ternaries 1 (nesting depth added 18). Most of this is not in the body itself: 2 of the 53 points are its own statements and the rest belongs to 8 function items inside it that branch (fire, a function literal at line 3081, a function literal at line 3132, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · jquery-1.10.2.defaultPrefilter (cognitive 53) · ×1
  • jquery-1.10.2.defaultPrefilter (cognitive 53) src/Library.UI/Scripts/jquery-1.10.2.js:8932 — jquery-1.10.2.defaultPrefilter has cognitive complexity 53 (threshold 15). Drivers by points: if/else 20 (39 pts), boolean chains 9, loops 3 (5 pts) (nesting depth added 21). Of this number, 49 points are the body's own statements and 4 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 · jquery-3.2.1.domManip (cognitive 51) · ×1
  • jquery-3.2.1.domManip (cognitive 51) src/Library.UI/Scripts/jquery-3.2.1.js:5506 — jquery-3.2.1.domManip has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (39 pts), loops 2 (7 pts), boolean chains 5 (nesting depth added 32). Of this number, 49 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-3.2.1.slim.domManip (cognitive 51) · ×1
  • jquery-3.2.1.slim.domManip (cognitive 51) src/Library.UI/Scripts/jquery-3.2.1.slim.js:5507 — jquery-3.2.1.slim.domManip has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (39 pts), loops 2 (7 pts), boolean chains 5 (nesting depth added 32). Of this number, 49 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.10.2.setMatcher (cognitive 49) · ×1
  • jquery-1.10.2.setMatcher (cognitive 49) src/Library.UI/Scripts/jquery-1.10.2.js:2547 — jquery-1.10.2.setMatcher has cognitive complexity 49 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 10, loops 3 (9 pts), ternaries 3 (4 pts) (nesting depth added 20). Most of this is not in the body itself: 4 of the 49 points are its own statements and the rest belongs to one function literal inside it that branches (line 2554). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · respond.applyMedia (cognitive 42) · ×1
  • respond.applyMedia (cognitive 42) src/Library.UI/Scripts/respond.js:97 — respond.applyMedia has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 11, loops 3 (nesting depth added 16). 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 · respond.matchmedia.addListener.applyMedia (cognitive 42) · ×1
  • respond.matchmedia.addListener.applyMedia (cognitive 42) src/Library.UI/Scripts/respond.matchmedia.addListener.js:146 — respond.matchmedia.addListener.applyMedia has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 11, loops 3 (nesting depth added 16). 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 · BaseEventHandler.AddEventLog (cognitive 41) · ×1
  • BaseEventHandler.AddEventLog (cognitive 41) src/Library.Domain.Core/BaseEventHandler.cs:38 — BaseEventHandler.AddEventLog has cognitive complexity 41 (threshold 15). Of this number, 40 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 · jquery-3.2.1.jQuery.Callbacks (cognitive 39) · ×1
  • jquery-3.2.1.jQuery.Callbacks (cognitive 39) src/Library.UI/Scripts/jquery-3.2.1.js:3186 — jquery-3.2.1.jQuery.Callbacks has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 8, loops 3 (4 pts), ternaries 1 (nesting depth added 11). None of this is in the body itself: all 39 points belong to 8 function items inside it that branch (fire, a function literal at line 3258, a function literal at line 3267, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · jquery-3.2.1.buildFragment (cognitive 39) · ×1
  • jquery-3.2.1.buildFragment (cognitive 39) src/Library.UI/Scripts/jquery-3.2.1.js:4599 — jquery-3.2.1.buildFragment has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 4 (9 pts), boolean chains 6, ternaries 1 (4 pts) (nesting depth added 19). 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 · jquery-3.2.1.slim.jQuery.Callbacks (cognitive 39) · ×1
  • jquery-3.2.1.slim.jQuery.Callbacks (cognitive 39) src/Library.UI/Scripts/jquery-3.2.1.slim.js:3187 — jquery-3.2.1.slim.jQuery.Callbacks has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 8, loops 3 (4 pts), ternaries 1 (nesting depth added 11). None of this is in the body itself: all 39 points belong to 8 function items inside it that branch (fire, a function literal at line 3259, a function literal at line 3268, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · jquery-3.2.1.slim.buildFragment (cognitive 39) · ×1
  • jquery-3.2.1.slim.buildFragment (cognitive 39) src/Library.UI/Scripts/jquery-3.2.1.slim.js:4600 — jquery-3.2.1.slim.buildFragment has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 4 (9 pts), boolean chains 6, ternaries 1 (4 pts) (nesting depth added 19). 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 · jquery-1.10.2.select (cognitive 37) · ×1
  • jquery-1.10.2.select (cognitive 37) src/Library.UI/Scripts/jquery-1.10.2.js:2830 — jquery-1.10.2.select has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (29 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-1.10.2.internalRemoveData (cognitive 35) · ×1
  • jquery-1.10.2.internalRemoveData (cognitive 35) src/Library.UI/Scripts/jquery-1.10.2.js:3632 — jquery-1.10.2.internalRemoveData has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (29 pts), loops 1 (3 pts), ternaries 2, boolean chains 1 (nesting depth added 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 · jquery-1.10.2.showHide (cognitive 35) · ×1
  • jquery-1.10.2.showHide (cognitive 35) src/Library.UI/Scripts/jquery-1.10.2.js:6762 — jquery-1.10.2.showHide has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 6, ternaries 1 (5 pts), loops 2 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-3.2.1.jQuery.ajaxTransport() (cognitive 31) · ×1
  • jquery-3.2.1.jQuery.ajaxTransport() (cognitive 31) src/Library.UI/Scripts/jquery-3.2.1.js:9085 — jquery-3.2.1.jQuery.ajaxTransport() has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 9, loops 2 (5 pts), error handling 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 9091, 9211, 9131, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · jquery-1.10.2.internalData (cognitive 27) · ×1
  • jquery-1.10.2.internalData (cognitive 27) src/Library.UI/Scripts/jquery-1.10.2.js:3545 — jquery-1.10.2.internalData has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 6, ternaries 2 (nesting depth added 4). 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 · jquery-1.10.2.matcherFromTokens (cognitive 26) · ×1
  • jquery-1.10.2.matcherFromTokens (cognitive 26) src/Library.UI/Scripts/jquery-1.10.2.js:2639 — jquery-1.10.2.matcherFromTokens has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 9, loops 2 (5 pts), ternaries 1 (nesting depth added 10). Of this number, 23 points are the body's own statements and 3 belong 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 · jquery-1.10.2.ajaxHandleResponses (cognitive 26) · ×1
  • jquery-1.10.2.ajaxHandleResponses (cognitive 26) src/Library.UI/Scripts/jquery-1.10.2.js:8187 — jquery-1.10.2.ajaxHandleResponses has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 10). 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 · jquery-3.2.1.ajaxHandleResponses (cognitive 26) · ×1
  • jquery-3.2.1.ajaxHandleResponses (cognitive 26) src/Library.UI/Scripts/jquery-3.2.1.js:8286 — jquery-3.2.1.ajaxHandleResponses has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 10). 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 · bootstrap.Tooltip.show (cognitive 25) · ×1
  • bootstrap.Tooltip.show (cognitive 25) src/Library.UI/Scripts/bootstrap.js:1395 — bootstrap.Tooltip.show has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 8, ternaries 3 (6 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 2 belong to one function item 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 · jquery-1.10.2.tokenize (cognitive 25) · ×1
  • jquery-1.10.2.tokenize (cognitive 25) src/Library.UI/Scripts/jquery-1.10.2.js:2386 — jquery-1.10.2.tokenize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 3 (5 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 10). 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 · jquery-3.2.1.access (cognitive 24) · ×1
  • jquery-3.2.1.access (cognitive 24) src/Library.UI/Scripts/jquery-3.2.1.js:3829 — jquery-3.2.1.access has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (5 pts), ternaries 2 (5 pts) (nesting depth added 11). 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 · jquery-3.2.1.showHide (cognitive 24) · ×1
  • jquery-3.2.1.showHide (cognitive 24) src/Library.UI/Scripts/jquery-3.2.1.js:4467 — jquery-3.2.1.showHide has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 2, loops 2 (nesting depth added 12). 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 · jquery-3.2.1.slim.access (cognitive 24) · ×1
  • jquery-3.2.1.slim.access (cognitive 24) src/Library.UI/Scripts/jquery-3.2.1.slim.js:3830 — jquery-3.2.1.slim.access has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (5 pts), ternaries 2 (5 pts) (nesting depth added 11). 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 · jquery-3.2.1.slim.showHide (cognitive 24) · ×1
  • jquery-3.2.1.slim.showHide (cognitive 24) src/Library.UI/Scripts/jquery-3.2.1.slim.js:4468 — jquery-3.2.1.slim.showHide has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 2, loops 2 (nesting depth added 12). 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 · bootstrap.Modal.backdrop (cognitive 23) · ×1
  • bootstrap.Modal.backdrop (cognitive 23) src/Library.UI/Scripts/bootstrap.js:1074 — bootstrap.Modal.backdrop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 4 (7 pts), boolean chains 5 (nesting depth added 7). Of this number, 16 points are the body's own statements and 7 belong to 2 function items 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 · jquery-1.10.2.jQuery.ready.promise (cognitive 22) · ×1
  • jquery-1.10.2.jQuery.ready.promise (cognitive 22) src/Library.UI/Scripts/jquery-1.10.2.js:921 — jquery-1.10.2.jQuery.ready.promise has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 2 (8 pts), boolean chains 2 (nesting depth added 12). Of this number, 13 points are the body's own statements and 9 belong 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 · jquery-1.10.2.fixCloneNodeIssues (cognitive 21) · ×1
  • jquery-1.10.2.fixCloneNodeIssues (cognitive 21) src/Library.UI/Scripts/jquery-1.10.2.js:6287 — jquery-1.10.2.fixCloneNodeIssues has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · respond.ripCSS (cognitive 21) · ×1
  • respond.ripCSS (cognitive 21) src/Library.UI/Scripts/respond.js:191 — respond.ripCSS has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jquery-3.2.1.Animation (cognitive 21) · ×1
  • jquery-3.2.1.Animation (cognitive 21) src/Library.UI/Scripts/jquery-3.2.1.js:6788 — jquery-3.2.1.Animation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, loops 3, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (tick, a function literal at line 6849, a function literal at line 6843). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · respond.matchmedia.addListener.ripCSS (cognitive 21) · ×1
  • respond.matchmedia.addListener.ripCSS (cognitive 21) src/Library.UI/Scripts/respond.matchmedia.addListener.js:240 — respond.matchmedia.addListener.ripCSS has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · respond.translate (cognitive 19) · ×1
  • respond.translate (cognitive 19) src/Library.UI/Scripts/respond.js:145 — respond.translate has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 4 (5 pts), loops 2 (3 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · jquery-3.2.1.adjustCSS (cognitive 19) · ×1
  • jquery-3.2.1.adjustCSS (cognitive 19) src/Library.UI/Scripts/jquery-3.2.1.js:4382 — jquery-3.2.1.adjustCSS has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 3 (4 pts), loops 1 (2 pts), ternaries 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · jquery-3.2.1.slim.adjustCSS (cognitive 19) · ×1
  • jquery-3.2.1.slim.adjustCSS (cognitive 19) src/Library.UI/Scripts/jquery-3.2.1.slim.js:4383 — jquery-3.2.1.slim.adjustCSS has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 3 (4 pts), loops 1 (2 pts), ternaries 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · respond.matchmedia.addListener.translate (cognitive 19) · ×1
  • respond.matchmedia.addListener.translate (cognitive 19) src/Library.UI/Scripts/respond.matchmedia.addListener.js:194 — respond.matchmedia.addListener.translate has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 4 (5 pts), loops 2 (3 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · bootstrap.Affix.getState (cognitive 18) · ×1
  • bootstrap.Affix.getState (cognitive 18) src/Library.UI/Scripts/bootstrap.js:2201 — bootstrap.Affix.getState has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (6 pts), boolean chains 3 (nesting depth added 5). 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 · jquery-1.10.2.augmentWidthOrHeight (cognitive 18) · ×1
  • jquery-1.10.2.augmentWidthOrHeight (cognitive 18) src/Library.UI/Scripts/jquery-1.10.2.js:7093 — jquery-1.10.2.augmentWidthOrHeight has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 9). 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 · jquery-1.10.2.Animation (cognitive 18) · ×1
  • jquery-1.10.2.Animation (cognitive 18) src/Library.UI/Scripts/jquery-1.10.2.js:8762 — jquery-1.10.2.Animation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, loops 3, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (tick, a function literal at line 8811, a function literal at line 8805). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · jquery-3.2.1.jQuery.speed (cognitive 18) · ×1
  • jquery-3.2.1.jQuery.speed (cognitive 18) src/Library.UI/Scripts/jquery-3.2.1.js:6951 — jquery-3.2.1.jQuery.speed has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 8, ternaries 1 (nesting depth added 3). 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 · jquery-1.10.2.getAll (cognitive 17) · ×1
  • jquery-1.10.2.getAll (cognitive 17) src/Library.UI/Scripts/jquery-1.10.2.js:6379 — jquery-1.10.2.getAll has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, if/else 3 (5 pts), ternaries 3 (4 pts), loops 1 (2 pts) (nesting depth added 4). 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 · jquery-3.2.1.augmentWidthOrHeight (cognitive 17) · ×1
  • jquery-3.2.1.augmentWidthOrHeight (cognitive 17) src/Library.UI/Scripts/jquery-3.2.1.js:6073 — jquery-3.2.1.augmentWidthOrHeight has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (nesting depth added 8). 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 · jquery-3.2.1.slim.augmentWidthOrHeight (cognitive 17) · ×1
  • jquery-3.2.1.slim.augmentWidthOrHeight (cognitive 17) src/Library.UI/Scripts/jquery-3.2.1.slim.js:6074 — jquery-3.2.1.slim.augmentWidthOrHeight has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (nesting depth added 8). 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 · jquery-1.10.2.propFilter (cognitive 16) · ×1
  • jquery-1.10.2.propFilter (cognitive 16) src/Library.UI/Scripts/jquery-1.10.2.js:8866 — jquery-1.10.2.propFilter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). 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 · jquery-3.2.1.on (cognitive 16) · ×1
  • jquery-3.2.1.on (cognitive 16) src/Library.UI/Scripts/jquery-3.2.1.js:4732 — jquery-3.2.1.on has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 3). 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 · jquery-3.2.1.propFilter (cognitive 16) · ×1
  • jquery-3.2.1.propFilter (cognitive 16) src/Library.UI/Scripts/jquery-3.2.1.js:6751 — jquery-3.2.1.propFilter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). 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 · jquery-3.2.1.jQuery.ajaxPrefilter("json jsonp") (cognitive 16) · ×1
  • jquery-3.2.1.jQuery.ajaxPrefilter("json jsonp") (cognitive 16) src/Library.UI/Scripts/jquery-3.2.1.js:9301 — jquery-3.2.1.jQuery.ajaxPrefilter("json jsonp") has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5 (nesting depth added 4). Of this number, 8 points are the body's own statements and 8 belong to 2 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 · jquery-3.2.1.slim.on (cognitive 16) · ×1
  • jquery-3.2.1.slim.on (cognitive 16) src/Library.UI/Scripts/jquery-3.2.1.slim.js:4733 — jquery-3.2.1.slim.on has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 3). 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) src/Library.SignalR/Hubs/CommandHub.cs:56 — src/Library.SignalR/Hubs/CommandHub.cs:56-76 | src/Library.SignalR/Library.SignalR/Hubs/CommandHub.cs:56-76 — before extracting anything, compare `src/Library.SignalR/Hubs/CommandHub.cs` and `src/Library.SignalR/Library.SignalR/Hubs/CommandHub.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:102 — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:102-120 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:120-138 | src/Library.UI/Utilities/ApiRequest.cs:103-121 — before extracting anything, compare `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs` and `src/Library.Infrastructure.Operation.Consul/ApiRequest.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) REDACTED:90 — REDACTED:90-107 | REDACTED:119-135 — 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 `REDACTED:90` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:119` calls `AddRange` and `REDACTED:90` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) src/Library.Service.Handler/Program.cs:78 — src/Library.Service.Handler/Program.cs:78-91 | src/Library.Service.Handler/Program.cs:97-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Library.Service.Handler/Program.cs:78` 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–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) src/Library.Domain.Core/BaseEventHandler.cs:49 — src/Library.Domain.Core/BaseEventHandler.cs:49-62 | src/Library.Domain.Core/BaseEventHandler.cs:63-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 8) · ×1
  • Duplicated block (12 lines × 8) src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:53 — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:53-64 | src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:76-87 | src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:53-64 | src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:98-109 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:53-64 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:76-87 | src/Library.UI/Utilities/ApiRequest.cs:54-65 | src/Library.UI/Utilities/ApiRequest.cs:77-88 — before extracting anything, compare `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs` and `src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:53` 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) REDACTED:219 — REDACTED:219-231 | REDACTED:218-230 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12–13 lines × 3) · ×1
  • Duplicated block (12–13 lines × 3) src/Library.Domain.Core/BaseEventHandler.cs:49 — src/Library.Domain.Core/BaseEventHandler.cs:49-60 | src/Library.Domain.Core/BaseEventHandler.cs:63-75 | src/Library.Domain.Core/BaseEventHandler.cs:78-89 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) REDACTED:183 — REDACTED:183-194 | REDACTED:172-183 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) REDACTED:198 — REDACTED:198-208 | REDACTED:192-202 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:198` 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 (22 lines × 4) · ×1
  • Duplicated block (22 lines × 4) src/Library.Service.Handler/AppsettingRabbitMQUrlProvider.cs:20 — src/Library.Service.Handler/AppsettingRabbitMQUrlProvider.cs:20-41 | src/Library.Service.Identity/AppsettingRabbitMQUrlProvider.cs:20-41 | src/Library.Service.Inventory/AppsettingRabbitMQUrlProvider.cs:20-41 | src/Library.Service.Rental/AppsettingRabbitMQUrlProvider.cs:20-41 — `src/Library.Service.Handler/AppsettingRabbitMQUrlProvider.cs` and `src/Library.Service.Identity/AppsettingRabbitMQUrlProvider.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 22 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Library.Service.Handler/AppsettingRabbitMQUrlProvider.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) src/Library.SignalR/Controllers/TrackController.cs:16 — src/Library.SignalR/Controllers/TrackController.cs:16-48 | src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs:16-48 — before extracting anything, compare `src/Library.SignalR/Controllers/TrackController.cs` and `src/Library.SignalR/Library.SignalR/Controllers/TrackController.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) src/Library.SignalR/Library.SignalR/Models/CommandResult.cs:14 — src/Library.SignalR/Library.SignalR/Models/CommandResult.cs:14-33 | src/Library.SignalR/Models/CommandResult.cs:14-33 — before extracting anything, compare `src/Library.SignalR/Library.SignalR/Models/CommandResult.cs` and `src/Library.SignalR/Models/CommandResult.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Library.SignalR/Library.SignalR/Models/CommandResult.cs:14` 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 × 4) · ×1
  • Duplicated block (11 lines × 4) src/Library.Service.Identity/Startup.cs:30 — src/Library.Service.Identity/Startup.cs:30-40 | src/Library.Service.Inventory/Startup.cs:30-40 | src/Library.Service.Logs/Startup.cs:34-44 | src/Library.Service.Rental/Startup.cs:41-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) REDACTED:16 — REDACTED:16-20 | src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQCommandSubscriber.cs:18-22 | REDACTED:16-20 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:15 — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:15-19 | src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:15-19 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:15-19 | src/Library.UI/Global.asax.cs:18-22 | src/Library.UI/Utilities/ApiRequest.cs:16-20 — before extracting anything, compare `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs` and `src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) REDACTED:173 — REDACTED:173-179 | REDACTED:151-157 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 10 separate duplicated blocks between them, totalling at least 117 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:91 — src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:91-98 | src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:109-116 | src/Library.UI/Utilities/ApiRequest.cs:92-99 — before extracting anything, compare `src/Library.Infrastructure.Core/Utilities/ApiRequest.cs` and `src/Library.Infrastructure.Operation.Consul/ApiRequest.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET netcoreapp2.0 src/Library.Service.Rental/Library.Service.Rental.csproj:4 — src/Library.Service.Rental/Library.Service.Rental.csproj declares .NET netcoreapp2.0 as this project's target framework, and .NET Core 2.0, support ended 2018-10-01. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2018-10-01 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits REDACTED:35 — `Login` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 20 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
S1 · Web-Security Posture · Obsolete TLS/SSL protocol version enabled · ×1
  • Obsolete TLS/SSL protocol version enabled src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:25 — `SecurityProtocol` explicitly selects `SecurityProtocolType.Tls`, a protocol version that is broken (SSL 2.0/3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Stop pinning versions here: leave the protocol unset (`SecurityProtocolType.SystemDefault`, or simply do not assign it) so the connection uses the OS policy and picks up TLS 1.3 and future versions without a code change. Where a version must be named explicitly, name `Tls12` and `Tls13` only.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×1
  • Sync-over-async (deadlock risk) src/Library.ApiGateway/Startup.cs:21 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Minor — 122 finding(s)
DM2 · Strongly-typed ids · Primitive id on a domain type · ×25
  • Primitive id on a domain type: BookRentedEvent.BookInventoryId src/Library.Service.Rental.Domain/Events/BookRentedEvent.cs:19 — `BookRentedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: BookReturnedEvent.BookId src/Library.Service.Rental.Domain/Events/BookReturnedEvent.cs:19 — `BookReturnedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestCreatedEvent.BookInventoryId src/Library.Service.Rental.Domain/Events/RentBookRequestCreatedEvent.cs:19 — `RentBookRequestCreatedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestSucceedEvent.BookInventoryId src/Library.Service.Rental.Domain/Events/RentBookRequestSucceedEvent.cs:19 — `RentBookRequestSucceedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestSucceedEvent.CustomerId src/Library.Service.Rental.Domain/Events/RentBookRequestSucceedEvent.cs:21 — `RentBookRequestSucceedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestAcceptedEvent.CustomerId src/Library.Service.Rental.Domain/Events/RentedBookOutStoredEvent.cs:16 — `RentBookRequestAcceptedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: ReturnBookRequestCreatedEvent.BookInventoryId src/Library.Service.Rental.Domain/Events/ReturnBookRequestCreatedEvent.cs:14 — `ReturnBookRequestCreatedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: ReturnBookRequestSucceedEvent.CustomerId src/Library.Service.Rental.Domain/Events/ReturnBookRequestSucceedEvent.cs:19 — `ReturnBookRequestSucceedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: ReturnBookRequestSucceedEvent.BookInventoryId src/Library.Service.Rental.Domain/Events/ReturnBookRequestSucceedEvent.cs:21 — `ReturnBookRequestSucceedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: BookInventory.BookId src/Library.Service.Inventory.Domain/BookInventory.cs:27 — `BookInventory.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: BookInventoryCreatedEvent.BookId src/Library.Service.Inventory.Domain/Events/BookInventoryCreatedEvent.cs:19 — `BookInventoryCreatedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: BookIssuedDateChangedEvent.BookId src/Library.Service.Inventory.Domain/Events/BookIssuedDateChangedEvent.cs:21 — `BookIssuedDateChangedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: BookNameChangedEvent.BookId src/Library.Service.Inventory.Domain/Events/BookNameChangedEvent.cs:21 — `BookNameChangedEvent.BookId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestAcceptedEvent.BookInventoryId src/Library.Service.Inventory.Domain/Events/RentBookRequestAcceptedEvent.cs:19 — `RentBookRequestAcceptedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestAcceptedEvent.CustomerId src/Library.Service.Inventory.Domain/Events/RentBookRequestAcceptedEvent.cs:23 — `RentBookRequestAcceptedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestSucceedEvent.BookInventoryId src/Library.Service.Inventory.Domain/Events/RentBookRequestSucceedEvent.cs:14 — `RentBookRequestSucceedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentBookRequestSucceedEvent.CustomerId src/Library.Service.Inventory.Domain/Events/RentBookRequestSucceedEvent.cs:16 — `RentBookRequestSucceedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: RentedBookOutStoredEvent.CustomerId src/Library.Service.Inventory.Domain/Events/RentedBookOutStoredEvent.cs:21 — `RentedBookOutStoredEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: ReturnBookRequestCreatedEvent.BookInventoryId src/Library.Service.Inventory.Domain/Events/ReturnBookRequestCreatedEvent.cs:19 — `ReturnBookRequestCreatedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: ReturnBookRequestSucceedEvent.CustomerId src/Library.Service.Inventory.Domain/Events/ReturnBookRequestSucceedEvent.cs:14 — `ReturnBookRequestSucceedEvent.CustomerId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: ReturnBookRequestSucceedEvent.BookInventoryId src/Library.Service.Inventory.Domain/Events/ReturnBookRequestSucceedEvent.cs:16 — `ReturnBookRequestSucceedEvent.BookInventoryId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: DomainEvent.EventKey src/Library.Domain.Core/DomainEvent.cs:20 — `DomainEvent.EventKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
  • Primitive id on a domain type: DomainEvent.AggregateId src/Library.Domain.Core/DomainEvent.cs:34 — `DomainEvent.AggregateId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: DomainEvent.CommandUniqueId src/Library.Domain.Core/DomainEvent.cs:40 — `DomainEvent.CommandUniqueId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
  • Primitive id on a domain type: AggregateRoot.AggregateRootId src/Library.Infrastructure.EventStorage.MongoDB/EventObject.cs:13 — `AggregateRoot.AggregateRootId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate src/Library.SignalR/Models/CommandResult.cs:24 — `EventResults.Count != 0 && EventResults.All(p => p.IsFinished)` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Models/CommandResult.cs, src/Library.SignalR/Models/CommandResult.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery.signalR-2.2.2.js:597 — `!!connection.withCredentials && isFirefox11OrGreater` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery.signalR-2.2.2.js, src/Library.SignalR/Scripts/jquery.signalR-2.2.2.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.UI/Scripts/jquery-1.10.2.js:8524 — `!!xhrSupported && ( "withCredentials" in xhrSupported )` appears character-identically in 2 files — src/Library.UI/Scripts/jquery-1.10.2.js, src/Library.UI/Scripts/jquery-3.2.1.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.UI/Scripts/respond.js:199 — `!/^([a-zA-Z:]*\/\/)/.test(href) && !base || href.replace(RegExp.$1, "").split("/")[0] === w.location.host` appears character-identically in 2 files — src/Library.UI/Scripts/respond.js, src/Library.UI/Scripts/respond.matchmedia.addListener.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery.signalR-2.2.2.js:894 — `!_pageLoaded && (!connection._.config || connection._.config.waitForPageLoad === true)` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery.signalR-2.2.2.js, src/Library.SignalR/Scripts/jquery.signalR-2.2.2.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery.signalR-2.2.2.js:467 — `!_pageLoaded && config.waitForPageLoad === true` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery.signalR-2.2.2.js, src/Library.SignalR/Scripts/jquery.signalR-2.2.2.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4581 — `!a.compareDocumentPosition || !b.compareDocumentPosition` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:8480 — `!box || !jQuery.contains( docElem, elem )` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.UI/Scripts/jquery-3.2.1.js:2476 — `!context && elem.ownerDocument !== document` appears character-identically in 2 files — src/Library.UI/Scripts/jquery-3.2.1.js, src/Library.UI/Scripts/jquery-3.2.1.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:5205 — `!cur || !cur.ownerDocument || cur === context || cur.nodeType === 11` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:1248 — `!div.addEventListener && div.attachEvent && div.fireEvent` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:4927 — `!div.getElementsByClassName || div.getElementsByClassName("e").length === 0` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.UI/Scripts/jquery-1.10.2.js:2253 — `!document.hasFocus || document.hasFocus()` appears character-identically in 3 files — src/Library.UI/Scripts/jquery-1.10.2.js, src/Library.UI/Scripts/jquery-3.2.1.js, src/Library.UI/Scripts/jquery-3.2.1.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6226 — `!elem || elem.nodeType === 3 || elem.nodeType === 8 || !elem.style` appears character-identically in 5 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.UI/Scripts/jquery-1.10.2.js, src/Library.UI/Scripts/jquery-3.2.1.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:2205 — `!elem || nType === 3 || nType === 8 || nType === 2` appears character-identically in 3 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.UI/Scripts/jquery-1.10.2.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:1961 — `!elem.className && classNames.length === 1` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6080 — `!elem.type || rscriptType.test( elem.type )` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.UI/Scripts/jquery-1.10.2.js:4810 — `!elemData || !(events = elemData.events)` appears character-identically in 2 files — src/Library.UI/Scripts/jquery-1.10.2.js, src/Library.UI/Scripts/jquery-3.2.1.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:2989 — `!event.relatedTarget && event.fromElement` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:3015 — `!event.which && event.button !== undefined` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:6258 — `!hooks || !("set" in hooks) || (value = hooks.set( elem, value )) !== undefined` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:2112 — `!hooks || !("set" in hooks) || hooks.set( this, val, "value" ) === undefined` appears character-identically in 3 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.UI/Scripts/jquery-1.10.2.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.UI/Scripts/jquery-1.10.2.js:2932 — `!isXML && elem.nodeName.toLowerCase() === "input"` appears character-identically in 3 files — src/Library.UI/Scripts/jquery-1.10.2.js, src/Library.UI/Scripts/jquery-3.2.1.js, src/Library.UI/Scripts/jquery-3.2.1.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:7897 — `!jQuery._data(elem, "olddisplay") && display === "none"` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js:1752 — `!jQuery.data( elem, queueDataKey, undefined, true ) && !jQuery.data( elem, markDataKey, undefined, true )` appears character-identically in 2 files — src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4.js, src/Library.SignalR/Scripts/jquery-1.6.4.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D34 · Knowledge Freshness · Orphaned file · ×21
  • Orphaned file src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/InventoryReportDataAccessor.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 REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.DataPersistence.Identity.SQLServer/IdentityReportDataAccessor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.DataPersistence.Rental.SQLServer/RentalReportDataAccessor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.Logger.SQLServer/Logger.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Service.Handler/AppsettingDBConnectionStringProvider.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.EventStorage.SQLServer/SQLServerEventStorage.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.EventStorage.MongoDB/MongoDBEventStorage.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.Operation.Consul/ApiRequest.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.Messaging.SignalR/ApiRequest.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Service.Handler/Program.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Service.Inventory/BooksController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/Extensions/ConvertExtension.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Infrastructure.Core/Utilities/ApiRequest.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.UI/Utilities/ApiRequest.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Service.Inventory.Domain/Book.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Service.Inventory.Domain/BookInventory.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.SignalR/Library.SignalR/Hubs/CommandHub.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.UI/Models/AccountViewModels.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Library.Domain.Core/BaseEventHandler.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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
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 src/Library.Service.Identity/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Library.Service.Inventory/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Library.Service.Logs/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Library.Service.Rental/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×5
  • No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected src/Library.Service.Identity/Program.cs:14 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected src/Library.Service.Inventory/Program.cs:14 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected src/Library.Service.Logs/Program.cs:14 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
  • No app-layer HTTPS enforcement detected src/Library.Service.Rental/Program.cs:14 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
IC1 · Incompleteness & stubs · Commented-out code · ×4
  • Commented-out code src/Library.Infrastructure.InjectionFramework/InjectContainer.cs:51 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:65 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Library.Infrastructure.Messaging.RabbitMQ/RabbitMQEventSubscriber.cs:69 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Library.UI/Views/Book/Add.cshtml:93 — A line of JavaScript has been commented out of this view's inline script rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch src/Library.SignalR/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:1925 — `jQuery.isPlainObject` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch src/Library.SignalR/Scripts/jquery-1.6.4-vsdoc.js:1925 — `jQuery.isPlainObject` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IInventoryReportDataAccessor (16 members) src/Library.Service.Inventory.Domain/DataAccessors/IInventoryReportDataAccessor.cs:9 — `IInventoryReportDataAccessor` declares 16 members: `GetAvailableBooks`, `AddBook`, `GetBooks`, `GetBookById`, `ExistISBN`, `UpdateBookName`, `UpdateBookDescription`, `UpdateBookISBN`, `UpdateBookIssuedDate`, `UpdateBookInventoryStatus`, `AddBookInventory`, `RemoveBookInventory`, `GetBookInventoryHistories`, `DeleteBook`, `Commit`, `CommitAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D18 · Solution Shape · Thin analysable surface across projects · ×1
  • Thin analysable surface across projects: Library.Infrastructure.CSDataAccessor.Rental src/Library.Infrastructure.CSDataAccessor.Rental/Library.Infrastructure.CSDataAccessor.Rental.csproj — 1 project(s) carry only a thin slice of real code; `Library.Infrastructure.CSDataAccessor.Rental` has 42 significant line(s). The mean analysable-surface weight is 99 %; this project lowers Solution Shape by about 0.06 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D21 · Naming Consistency · Typo in event handler name · ×1
  • Typo in event handler name: 'BookIssuedDatehangedEventHandler' is missing the 'C' in 'Changed', whereas similar handlers like 'BookISBNChangedEventHandler' and the event 'BookNameChangedEvent' use the correct spelling. This creates a visual inconsistency and potential maintenance confusion. — Rename to 'BookIssuedDateChangedEventHandler' to match the 'Changed' suffix convention used by other event handlers and events in the same namespace. (symbols: Type: Library.Service.Inventory.Domain.EventHandlers.BookIssuedDatehangedEventHandler, Type: Library.Service.Inventory.Domain.EventHandlers.BookISBNChangedEventHandler, Type: Library.Service.Inventory.Domain.EventHandlers.BookNameChangedEvent)
D21 · Naming Consistency · Spelling error in event name · ×1
  • Spelling error in event name: 'CustomerOwnedBookExcceedEvent' contains a typo ('Excceed' with double 'e'), while other status/result events like 'BookInventoryOutputFailedEvent' and 'ReturnBookRequestSucceedEvent' are spelled correctly. This breaks the consistent vocabulary of event naming. — Rename to 'CustomerOwnedBookExceedEvent' to correct the spelling and align with standard English usage found in other event names. (symbols: Type: Library.Service.Rental.Domain.Events.CustomerOwnedBookExcceedEvent, Type: Library.Service.Inventory.Domain.Events.BookInventoryOutputFailedEvent, Type: Library.Service.Rental.Domain.Events.ReturnBookRequestSucceedEvent)
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 21 of 21 significant files have no living knowledge — the codebase as a whole is dormant, not 21 separate risks. Counted over 21 of the 254 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D9 · Test Distribution · No tests found · ×1
  • No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift README.md:2 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
S1 · Web-Security Posture · Secure cookie flags not detected · ×1
  • Secure cookie flags not detected REDACTED:51 — No CookieSecurePolicy/HttpOnly/SameSite configuration found. (−1.5 on this card; skip if the app sets no cookies.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 0/6 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.
Minor — 28 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×28
  • XML-doc coverage: Library.Service.Identity src/Library.Service.Identity/Library.Service.Identity.csproj — Library.Service.Identity: 0 % XML-doc coverage (0/33).
  • XML-doc coverage: Library.Service.Identity.Domain src/Library.Service.Identity.Domain/Library.Service.Identity.Domain.csproj — Library.Service.Identity.Domain: 0 % XML-doc coverage (0/44).
  • XML-doc coverage: Library.Service.Rental.Domain src/Library.Service.Rental.Domain/Library.Service.Rental.Domain.csproj — Library.Service.Rental.Domain: 0 % XML-doc coverage (0/127).
  • XML-doc coverage: Library.Service.Rental src/Library.Service.Rental/Library.Service.Rental.csproj — Library.Service.Rental: 0 % XML-doc coverage (0/27).
  • XML-doc coverage: Library.Service.Inventory src/Library.Service.Inventory/Library.Service.Inventory.csproj — Library.Service.Inventory: 0 % XML-doc coverage (0/38).
  • XML-doc coverage: Library.Service.Inventory.Domain src/Library.Service.Inventory.Domain/Library.Service.Inventory.Domain.csproj — Library.Service.Inventory.Domain: 0 % XML-doc coverage (0/238).
  • XML-doc coverage: Library.Domain.Core src/Library.Domain.Core/Library.Domain.Core.csproj — Library.Domain.Core: 0 % XML-doc coverage (0/101).
  • XML-doc coverage: Library.Infrastructure.Messaging.RabbitMQ src/Library.Infrastructure.Messaging.RabbitMQ/Library.Infrastructure.Messaging.RabbitMQ.csproj — Library.Infrastructure.Messaging.RabbitMQ: 0 % XML-doc coverage (0/17).
  • XML-doc coverage: Library.Service.Handler src/Library.Service.Handler/Library.Service.Handler.csproj — Library.Service.Handler: 0 % XML-doc coverage (0/40).
  • XML-doc coverage: Library.Infrastructure.Messaging.SignalR src/Library.Infrastructure.Messaging.SignalR/Library.Infrastructure.Messaging.SignalR.csproj — Library.Infrastructure.Messaging.SignalR: 0 % XML-doc coverage (0/15).
  • XML-doc coverage: Library.Infrastructure.InjectionFramework src/Library.Infrastructure.InjectionFramework/Library.Infrastructure.InjectionFramework.csproj — Library.Infrastructure.InjectionFramework: 0 % XML-doc coverage (0/7).
  • XML-doc coverage: Library.Infrastructure.EventStorage.SQLServer src/Library.Infrastructure.EventStorage.SQLServer/Library.Infrastructure.EventStorage.SQLServer.csproj — Library.Infrastructure.EventStorage.SQLServer: 69 % XML-doc coverage (11/16).
  • XML-doc coverage: Library.Infrastructure.DataPersistence.Inventory.SQLServer src/Library.Infrastructure.DataPersistence.Inventory.SQLServer/Library.Infrastructure.DataPersistence.Inventory.SQLServer.csproj — Library.Infrastructure.DataPersistence.Inventory.SQLServer: 0 % XML-doc coverage (0/27).
  • XML-doc coverage: Library.Infrastructure.DataPersistence.Identity.SQLServer src/Library.Infrastructure.DataPersistence.Identity.SQLServer/Library.Infrastructure.DataPersistence.Identity.SQLServer.csproj — Library.Infrastructure.DataPersistence.Identity.SQLServer: 0 % XML-doc coverage (0/12).
  • XML-doc coverage: Library.Infrastructure.DataPersistence.Rental.SQLServer src/Library.Infrastructure.DataPersistence.Rental.SQLServer/Library.Infrastructure.DataPersistence.Rental.SQLServer.csproj — Library.Infrastructure.DataPersistence.Rental.SQLServer: 0 % XML-doc coverage (0/12).
  • XML-doc coverage: Library.Infrastructure.DataPersistence.Core.SQLServer src/Library.Infrastructure.DataPersistence.Core.SQLServer/Library.Infrastructure.DataPersistence.Core.SQLServer.csproj — Library.Infrastructure.DataPersistence.Core.SQLServer: 0 % XML-doc coverage (0/18).
  • XML-doc coverage: Library.UI src/Library.UI/Library.UI.csproj — Library.UI: 0 % XML-doc coverage (0/210).
  • XML-doc coverage: Library.SignalR src/Library.SignalR/Library.SignalR.csproj — Library.SignalR: 0 % XML-doc coverage (0/42).
  • XML-doc coverage: Library.Infrastructure.Core src/Library.Infrastructure.Core/Library.Infrastructure.Core.csproj — Library.Infrastructure.Core: 0 % XML-doc coverage (0/8).
  • XML-doc coverage: Library.Infrastructure.Logger.SQLServer src/Library.Infrastructure.Logger.SQLServer/Library.Infrastructure.Logger.SQLServer.csproj — Library.Infrastructure.Logger.SQLServer: 0 % XML-doc coverage (0/14).
  • XML-doc coverage: Library.Service.Logs src/Library.Service.Logs/Library.Service.Logs.csproj — Library.Service.Logs: 0 % XML-doc coverage (0/16).
  • XML-doc coverage: Library.Infrastructure.EventStorage.MongoDB src/Library.Infrastructure.EventStorage.MongoDB/Library.Infrastructure.EventStorage.MongoDB.csproj — Library.Infrastructure.EventStorage.MongoDB: 0 % XML-doc coverage (0/22).
  • XML-doc coverage: Library.Infrastructure.Operation.Core src/Library.Infrastructure.Operation.Core/Library.Infrastructure.Operation.Core.csproj — Library.Infrastructure.Operation.Core: 0 % XML-doc coverage (0/10).
  • XML-doc coverage: Library.Infrastructure.Operation.Consul src/Library.Infrastructure.Operation.Consul/Library.Infrastructure.Operation.Consul.csproj — Library.Infrastructure.Operation.Consul: 0 % XML-doc coverage (0/23).
  • XML-doc coverage: Library.ApiGateway src/Library.ApiGateway/Library.ApiGateway.csproj — Library.ApiGateway: 0 % XML-doc coverage (0/5).
  • + 3 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a9f65fe32daa45b9919d8213115c85b9/history.json --exit-code 0 --source .0artifacts/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-a9f65fe32daa45b9919d8213115c85b9/tree.json --exit-code 0 --source .0artifacts/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 .61artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .10artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .23artifacts/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 1 file(s) — `src/Library.UI/Scripts/_references.js` — 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 & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

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

Name — 16 field(s)
  • PersonName.FirstName src/Library.Domain.Core/ValueObjects/PersonName.cs:12
  • PersonName.LastName src/Library.Domain.Core/ValueObjects/PersonName.cs:14
  • CustomerListViewModel.FirstName src/Library.Service.Identity.Domain/ViewModels/CustomerListViewModel.cs:9
  • CustomerListViewModel.LastName src/Library.Service.Identity.Domain/ViewModels/CustomerListViewModel.cs:11
  • IdentityDetailsViewModel.FirstName src/Library.Service.Identity.Domain/ViewModels/IdentityDetailsViewModel.cs:9
  • IdentityDetailsViewModel.LastName src/Library.Service.Identity.Domain/ViewModels/IdentityDetailsViewModel.cs:11
  • CustomerDTO.FirstName src/Library.Service.Identity/DTOs/CustomerDTO.cs:13
  • CustomerDTO.LastName src/Library.Service.Identity/DTOs/CustomerDTO.cs:17
  • UnreturnedBookViewModel.FirstName src/Library.Service.Rental.Domain/ViewModels/UnreturnedBookViewModel.cs:15
  • UnreturnedBookViewModel.LastName src/Library.Service.Rental.Domain/ViewModels/UnreturnedBookViewModel.cs:17
  • IdentityDetailsDTO.FirstName src/Library.UI/DTOs/IdentityDetailsDTO.cs:9
  • IdentityDetailsDTO.LastName src/Library.UI/DTOs/IdentityDetailsDTO.cs:11
  • CustomerViewModel.FirstName src/Library.UI/ViewModels/CustomerViewModel.cs:9
  • CustomerViewModel.LastName src/Library.UI/ViewModels/CustomerViewModel.cs:11
  • UnreturnedBookViewModel.FirstName src/Library.UI/ViewModels/UnreturnedBookViewModel.cs:15
  • UnreturnedBookViewModel.LastName src/Library.UI/ViewModels/UnreturnedBookViewModel.cs:17
Email — 5 field(s)
  • ExternalLoginConfirmationViewModel.Email src/Library.UI/Models/AccountViewModels.cs:10
  • ForgotViewModel.Email src/Library.UI/Models/AccountViewModels.cs:47
  • RegisterViewModel.Email src/Library.UI/Models/AccountViewModels.cs:67
  • ResetPasswordViewModel.Email src/Library.UI/Models/AccountViewModels.cs:86
  • ForgotPasswordViewModel.Email src/Library.UI/Models/AccountViewModels.cs:107
Phone — 2 field(s)
  • IndexViewModel.PhoneNumber src/Library.UI/Models/ManageViewModels.cs:12
  • VerifyPhoneNumberViewModel.PhoneNumber src/Library.UI/Models/ManageViewModels.cs:78

Issues: 123 · Warnings: 429 · Recommendations: 122 · Info: 28 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 09:30 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md