Public report of rygel/AIUsageTracker, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert 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, 17 November 2026, 10:09 UTC · Survey ID cd_2536c0c2b2b24b53a4a22624587dc2ec
rygel/AIUsageTracker
Measured 17 November 2026, 10:08 UTC, at code version d011abf
Code coverage is not measured: Suite not runnable in-image.
Test reliability is not measured: No test run produced results.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 37,201 lines of product code in 10 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Accessibility, 24.9
Findings by how serious they are
89 critical330 serious120 minor
1 dimension is left out of the score. we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. It counts neither for nor against the score, and Limitations lists it with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 10:08 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work 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 ▸
77of 77 dimensions measured by tools.
498of 539 findings point to an exact file and line, so you can open each one in the code. The other 41 concern the repository as a whole, such as missing documentation.
77dimensions across 7 lenses, read from 37,201 lines of product code in 10 projects.
rygel/AIUsageTracker falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 36.4 out of 100 and is rated Weak, and 25 of its 89 critical findings are security problems.
Accessibility, at 24.9, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 6.5 points. Adding text alternatives would lift Accessibility itself, worth about 4.9 points. Raising Accessibility to 70 would lift the score to about 46.0.
Eight passwords or keys in the code's history and five in the code are open to anyone who can read the repository. Six weaknesses in the code could be used by an attacker, and three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Replacing each exposed password or key, fixing the weaknesses the scanner points to and pinning each tool to an exact version would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The 48 analysis rules switched off in the settings need switching back on in the settings file.
The product code is 37,201 lines, about €96,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 24.9 to 70, the lowest score rated Strong, the score would rise from 36.4 to about 46.0.
Code composition: what the lines of code are
Business logic 32%Supporting code 21%Tests 46%
Rebuild cost: about €96,000 · Estimate
Cost to rebuild
€31,000 to €160,000, for 525 to 1,698 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, 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 36. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 37,201 lines of product code
Comment lines
The estimate prices 34,811 lines. Comment lines count towards the size of 37,201 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price 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
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 6.5 points · Medium effort · Access Controls
2
Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (3), REDACTED.
Raises the score by about 3.0 points · Low effort · Secrets (history)
3
Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5).
Raises the score by about 2.9 points · Low effort · REDACTED 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 €96,000 to build again, about 0.7 person-years of work. Its weakest lens is Accessibility, at 24.9 (Critical). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. Of all the actions in this report, it raises the score most for the work it takes: about 6.5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
38 modules, with 60 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
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.
AIUsageTracker.Core.MonitorClient uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Core.MonitorClient, while a change to AIUsageTracker.Core.MonitorClient can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Core.MonitorClient uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Extensions uses AIUsageTracker.Core.Exceptions, so a change to AIUsageTracker.Core.Exceptions can break AIUsageTracker.Infrastructure.Extensions, while a change to AIUsageTracker.Infrastructure.Extensions can't break AIUsageTracker.Core.Exceptions.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Extensions uses a module listed above it, which is the healthy direction.
AIUsageTracker.Core.Interfaces uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Core.Interfaces, while a change to AIUsageTracker.Core.Interfaces can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Core.Interfaces uses a module listed above it, which is the healthy direction.
AIUsageTracker.Core.Interfaces uses AIUsageTracker.Core.MonitorClient, so a change to AIUsageTracker.Core.MonitorClient can break AIUsageTracker.Core.Interfaces, while a change to AIUsageTracker.Core.Interfaces can't break AIUsageTracker.Core.MonitorClient.
Position
Below the diagonal: AIUsageTracker.Core.Interfaces uses a module listed above it, which is the healthy direction.
AIUsageTracker.Core.Providers uses AIUsageTracker.Core.Exceptions, so a change to AIUsageTracker.Core.Exceptions can break AIUsageTracker.Core.Providers, while a change to AIUsageTracker.Core.Providers can't break AIUsageTracker.Core.Exceptions.
Position
Below the diagonal: AIUsageTracker.Core.Providers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Core.Providers uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Core.Providers, while a change to AIUsageTracker.Core.Providers can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Core.Providers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Core.Providers uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Core.Providers, while a change to AIUsageTracker.Core.Providers can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Core.Providers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Core.Services uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Core.Services, while a change to AIUsageTracker.Core.Services can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Core.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Core.Services uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Core.Services, while a change to AIUsageTracker.Core.Services can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Core.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Configuration uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Infrastructure.Configuration, while a change to AIUsageTracker.Infrastructure.Configuration can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Configuration uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Infrastructure.Configuration, while a change to AIUsageTracker.Infrastructure.Configuration can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Configuration uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Helpers uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Infrastructure.Helpers, while a change to AIUsageTracker.Infrastructure.Helpers can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Helpers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Mappers uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Infrastructure.Mappers, while a change to AIUsageTracker.Infrastructure.Mappers can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Mappers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Mappers uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Infrastructure.Mappers, while a change to AIUsageTracker.Infrastructure.Mappers can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Mappers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.MonitorClient uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Infrastructure.MonitorClient, while a change to AIUsageTracker.Infrastructure.MonitorClient can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Infrastructure.MonitorClient uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.MonitorClient uses AIUsageTracker.Core.MonitorClient, so a change to AIUsageTracker.Core.MonitorClient can break AIUsageTracker.Infrastructure.MonitorClient, while a change to AIUsageTracker.Infrastructure.MonitorClient can't break AIUsageTracker.Core.MonitorClient.
Position
Below the diagonal: AIUsageTracker.Infrastructure.MonitorClient uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.MonitorClient uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Infrastructure.MonitorClient, while a change to AIUsageTracker.Infrastructure.MonitorClient can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Infrastructure.MonitorClient uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Services uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Infrastructure.Services, while a change to AIUsageTracker.Infrastructure.Services can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Services uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Infrastructure.Services, while a change to AIUsageTracker.Infrastructure.Services can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Logging uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Monitor.Logging, while a change to AIUsageTracker.Monitor.Logging can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Monitor.Logging uses a module listed above it, which is the healthy direction.
AIUsageTracker.CLI uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.CLI, while a change to AIUsageTracker.CLI can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.CLI uses a module listed above it, which is the healthy direction.
AIUsageTracker.CLI uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.CLI, while a change to AIUsageTracker.CLI can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.CLI uses a module listed above it, which is the healthy direction.
AIUsageTracker.CLI uses AIUsageTracker.Infrastructure.MonitorClient, so a change to AIUsageTracker.Infrastructure.MonitorClient can break AIUsageTracker.CLI, while a change to AIUsageTracker.CLI can't break AIUsageTracker.Infrastructure.MonitorClient.
Position
Below the diagonal: AIUsageTracker.CLI uses a module listed above it, which is the healthy direction.
64 pairs of types, where a type in AIUsageTracker.Infrastructure.Providers uses a type in AIUsageTracker.Core.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
AIUsageTracker.Infrastructure.Providers uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Infrastructure.Providers, while a change to AIUsageTracker.Infrastructure.Providers can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Providers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Providers uses AIUsageTracker.Core.MonitorClient, so a change to AIUsageTracker.Core.MonitorClient can break AIUsageTracker.Infrastructure.Providers, while a change to AIUsageTracker.Infrastructure.Providers can't break AIUsageTracker.Core.MonitorClient.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Providers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Providers uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Infrastructure.Providers, while a change to AIUsageTracker.Infrastructure.Providers can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Providers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Infrastructure.Providers uses AIUsageTracker.Core.Providers, so a change to AIUsageTracker.Core.Providers can break AIUsageTracker.Infrastructure.Providers, while a change to AIUsageTracker.Infrastructure.Providers can't break AIUsageTracker.Core.Providers.
Position
Below the diagonal: AIUsageTracker.Infrastructure.Providers uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Monitor, while a change to AIUsageTracker.Monitor can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Monitor uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor uses AIUsageTracker.Infrastructure.MonitorClient, so a change to AIUsageTracker.Infrastructure.MonitorClient can break AIUsageTracker.Monitor, while a change to AIUsageTracker.Monitor can't break AIUsageTracker.Infrastructure.MonitorClient.
Position
Below the diagonal: AIUsageTracker.Monitor uses a module listed above it, which is the healthy direction.
38 pairs of types, where a type in AIUsageTracker.Monitor.Services uses a type in AIUsageTracker.Core.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
AIUsageTracker.Monitor.Services uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Monitor.Services, while a change to AIUsageTracker.Monitor.Services can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Monitor.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Services uses AIUsageTracker.Monitor.Hubs, so a change to AIUsageTracker.Monitor.Hubs can break AIUsageTracker.Monitor.Services, while a change to AIUsageTracker.Monitor.Services can't break AIUsageTracker.Monitor.Hubs.
Position
Below the diagonal: AIUsageTracker.Monitor.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Services uses AIUsageTracker.Core.MonitorClient, so a change to AIUsageTracker.Core.MonitorClient can break AIUsageTracker.Monitor.Services, while a change to AIUsageTracker.Monitor.Services can't break AIUsageTracker.Core.MonitorClient.
Position
Below the diagonal: AIUsageTracker.Monitor.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Services uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Monitor.Services, while a change to AIUsageTracker.Monitor.Services can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Monitor.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Services uses AIUsageTracker.Core.Services, so a change to AIUsageTracker.Core.Services can break AIUsageTracker.Monitor.Services, while a change to AIUsageTracker.Monitor.Services can't break AIUsageTracker.Core.Services.
Position
Below the diagonal: AIUsageTracker.Monitor.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Services uses AIUsageTracker.Infrastructure.Configuration, so a change to AIUsageTracker.Infrastructure.Configuration can break AIUsageTracker.Monitor.Services, while a change to AIUsageTracker.Monitor.Services can't break AIUsageTracker.Infrastructure.Configuration.
Position
Below the diagonal: AIUsageTracker.Monitor.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim.Services uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.UI.Slim.Services, while a change to AIUsageTracker.UI.Slim.Services can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.UI.Slim.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim.Services uses AIUsageTracker.Infrastructure.Services, so a change to AIUsageTracker.Infrastructure.Services can break AIUsageTracker.UI.Slim.Services, while a change to AIUsageTracker.UI.Slim.Services can't break AIUsageTracker.Infrastructure.Services.
Position
Below the diagonal: AIUsageTracker.UI.Slim.Services uses a module listed above it, which is the healthy direction.
33→38 AIUsageTracker.UI.Slim.Services uses AIUsageTracker.UI.Slimpart of a loop✕
Connections
3 pairs of types, where a type in AIUsageTracker.UI.Slim.Services uses a type in AIUsageTracker.UI.Slim.
AIUsageTracker.UI.Slim.Services uses AIUsageTracker.UI.Slim, so a change to AIUsageTracker.UI.Slim can break AIUsageTracker.UI.Slim.Services, while a change to AIUsageTracker.UI.Slim.Services can't break AIUsageTracker.UI.Slim.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
AIUsageTracker.Web.Services uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Web.Services, while a change to AIUsageTracker.Web.Services can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Web.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Services uses AIUsageTracker.Core.MonitorClient, so a change to AIUsageTracker.Core.MonitorClient can break AIUsageTracker.Web.Services, while a change to AIUsageTracker.Web.Services can't break AIUsageTracker.Core.MonitorClient.
Position
Below the diagonal: AIUsageTracker.Web.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Services uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Web.Services, while a change to AIUsageTracker.Web.Services can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Web.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Services uses AIUsageTracker.Infrastructure.MonitorClient, so a change to AIUsageTracker.Infrastructure.MonitorClient can break AIUsageTracker.Web.Services, while a change to AIUsageTracker.Web.Services can't break AIUsageTracker.Infrastructure.MonitorClient.
Position
Below the diagonal: AIUsageTracker.Web.Services uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Endpoints uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Monitor.Endpoints, while a change to AIUsageTracker.Monitor.Endpoints can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Monitor.Endpoints uses a module listed above it, which is the healthy direction.
AIUsageTracker.Monitor.Endpoints uses AIUsageTracker.Monitor.Services, so a change to AIUsageTracker.Monitor.Services can break AIUsageTracker.Monitor.Endpoints, while a change to AIUsageTracker.Monitor.Endpoints can't break AIUsageTracker.Monitor.Services.
Position
Below the diagonal: AIUsageTracker.Monitor.Endpoints uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim.ViewModels uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.UI.Slim.ViewModels, while a change to AIUsageTracker.UI.Slim.ViewModels can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.UI.Slim.ViewModels uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim.ViewModels uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.UI.Slim.ViewModels, while a change to AIUsageTracker.UI.Slim.ViewModels can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.UI.Slim.ViewModels uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim.ViewModels uses AIUsageTracker.UI.Slim.Services, so a change to AIUsageTracker.UI.Slim.Services can break AIUsageTracker.UI.Slim.ViewModels, while a change to AIUsageTracker.UI.Slim.ViewModels can't break AIUsageTracker.UI.Slim.Services.
Position
Below the diagonal: AIUsageTracker.UI.Slim.ViewModels uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Pages uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.Web.Pages, while a change to AIUsageTracker.Web.Pages can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.Web.Pages uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Pages uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.Web.Pages, while a change to AIUsageTracker.Web.Pages can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.Web.Pages uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Pages uses AIUsageTracker.Core.Services, so a change to AIUsageTracker.Core.Services can break AIUsageTracker.Web.Pages, while a change to AIUsageTracker.Web.Pages can't break AIUsageTracker.Core.Services.
Position
Below the diagonal: AIUsageTracker.Web.Pages uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Pages uses AIUsageTracker.Infrastructure.Configuration, so a change to AIUsageTracker.Infrastructure.Configuration can break AIUsageTracker.Web.Pages, while a change to AIUsageTracker.Web.Pages can't break AIUsageTracker.Infrastructure.Configuration.
Position
Below the diagonal: AIUsageTracker.Web.Pages uses a module listed above it, which is the healthy direction.
AIUsageTracker.Web.Pages uses AIUsageTracker.Web.Services, so a change to AIUsageTracker.Web.Services can break AIUsageTracker.Web.Pages, while a change to AIUsageTracker.Web.Pages can't break AIUsageTracker.Web.Services.
Position
Below the diagonal: AIUsageTracker.Web.Pages uses a module listed above it, which is the healthy direction.
49 pairs of types, where a type in AIUsageTracker.UI.Slim uses a type in AIUsageTracker.Core.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
AIUsageTracker.UI.Slim uses AIUsageTracker.Core.Models, so a change to AIUsageTracker.Core.Models can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.Core.Models.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim uses AIUsageTracker.Core.MonitorClient, so a change to AIUsageTracker.Core.MonitorClient can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.Core.MonitorClient.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim uses AIUsageTracker.Core.Interfaces, so a change to AIUsageTracker.Core.Interfaces can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.Core.Interfaces.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim uses AIUsageTracker.Infrastructure.Configuration, so a change to AIUsageTracker.Infrastructure.Configuration can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.Infrastructure.Configuration.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim uses AIUsageTracker.Infrastructure.MonitorClient, so a change to AIUsageTracker.Infrastructure.MonitorClient can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.Infrastructure.MonitorClient.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim uses AIUsageTracker.Infrastructure.Services, so a change to AIUsageTracker.Infrastructure.Services can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.Infrastructure.Services.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim uses AIUsageTracker.UI.Slim.Services, so a change to AIUsageTracker.UI.Slim.Services can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.UI.Slim.Services.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
AIUsageTracker.UI.Slim uses AIUsageTracker.UI.Slim.ViewModels, so a change to AIUsageTracker.UI.Slim.ViewModels can break AIUsageTracker.UI.Slim, while a change to AIUsageTracker.UI.Slim can't break AIUsageTracker.UI.Slim.ViewModels.
Position
Below the diagonal: AIUsageTracker.UI.Slim uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 — Authentication Failures
14
High / Critical
A05:2025 — Injection
13
High / Critical
A03:2025 — Software Supply Chain Failures
5
Medium
Roadmap
Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; 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; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
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.
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.
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with AIUsageTracker.Monitor.Tests.csproj, AIUsageTracker.Tests.csproj, AIUsageTracker.Web.Tests.csproj.
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 — 89
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 — 330
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 — 120
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 1
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
This survey 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. All 77 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 77 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 498 of 539 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We 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. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`dotnet test AIUsageTracker.Tests\AIUsageTracker.Tests.csproj…`), uploaded by `codecov/codecov-action` shows that coverage is collected and tracked in your own CI. The suite could not be built/run in-image, so the number could not be read here — it is excluded from the score rather than treated as unmeasured-by-the-team. To have it measured, make the suite runnable without services we do not provision (a database, a broker). For context only, test code is ≈ 81% of production LoC (30,129 test / 37,095 production) — a rough proxy, NOT a coverage measurement. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
D11 Test Reliability — not measured this run — We 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. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
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 — We 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 (37,095 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"]`.
D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `AIUsageTracker.Infrastructure/Configuration/AtomicFileWriter.cs`, `AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs`, `AIUsageTracker.Monitor/Endpoints/MonitorDiagnosticsSnapshotFactory.cs`, `AIUsageTracker.Monitor/Services/MonitorJobScheduler.cs` 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.
AXR1 Runtime accessibility — not measured this run — We 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. User interface: 10 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: the service booted and answers HTTP at http://127.0.0.1:5000, but serves no HTML page — nothing for the accessibility crawl.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 254 further occurrence(s) are not listed individually; the score already reflects all 294.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
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.
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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MainWindowRuntimeLogic.BuildTooltipContent at 27. A further 2 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 ProviderBase.CreateUnavailableUsageFromProviderException at 19 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: AIUsageTracker.Core/Providers/ProviderBase.cs (ProviderBase.CreateUnavailableUsageFromProviderException at 19), AIUsageTracker.UI.Slim/MainWindow.Rendering.cs (MainWindow.ShowStatus at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MainWindowRuntimeLogic.BuildTooltipContent (cyclomatic 27), ProviderUsageProcessingPipeline.NormalizeUsage (cyclomatic 26), MainWindowRuntimeLogic.Create (cyclomatic 18). — 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 3 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with MainWindowRuntimeLogic.BuildTooltipContent (cognitive 40). — Refactoring it lifts Cognitive Complexity from 8.2 to about 8.5/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 9 TooManyMethods finding(s) in God Classes — start with SettingsWindow.xaml.cs, MainWindow.xaml.cs, MonitorService.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 5 FileTooLong finding(s) in God Classes — start with SettingsWindow.Providers.cs, SettingsWindow.xaml.cs, AntigravityProvider.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 MethodTooLong finding(s) in God Classes — start with CardCatalogPermutations.cs, MainWindowRuntimeLogic.Presentation.cs, GroqProvider.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
13 duplicated block group(s) detected. 4.8 % of the production lines (1,777 of 37,095) are in a reported copy. A further 41 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 54 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (15 corresponding lines) · ×5AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs:143
Edited copy of a member (26 corresponding lines) · ×3AIUsageTracker.Infrastructure/Configuration/TokenDiscoveryService.cs:243
Edited copy of a member (14 corresponding lines) · ×3AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:185
Edited copy of a member (12 corresponding lines) · ×3AIUsageTracker.UI.Slim/MainWindow.xaml.cs:541
Edited copy of a member (11 corresponding lines) · ×3AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:691
+ 29 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with AgentGroupedUsageValueResolver.cs (2), MinimaxProvider.cs, SettingsWindow.xaml.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Edited copy of a member (26 corresponding lines) finding(s) in Code Duplication — start with TokenDiscoveryService.cs (2), CodexProvider.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with OpenCodeZenProvider.cs, CodexProvider.cs, InfoDialog.xaml.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
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.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SettingsWindow.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 6 mechanizable ADR(s) are enforced: 6 by analyzers, 0 by tests. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 18 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
Resolve the 17 Test cannot fail finding(s) in Test Quality — start with AttachedBehaviorTests.cs (6), DialogOpenBehaviorTests.cs (6), PrivacyButtonBehaviorTests.cs (5). — One of this dimension's main actionable groups (17 warning-level).
Resolve the 1 No assertions finding(s) in Test Quality — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with AIUsageTracker.Monitor.Tests.csproj, AIUsageTracker.Tests.csproj, AIUsageTracker.Web.Tests.csproj. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with AIUsageTracker.UI.Slim.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 5 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 230 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 31 direct `PackageReference`(s), and 175 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs (13×27=351); AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs (10×18=180); AIUsageTracker.Monitor/Services/ProviderUsageProcessingPipeline.cs (6×26=156) Repeated repair below the complexity floor: AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs (5 of 8 changes were fixes); AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs (4 of 7 changes were fixes); AIUsageTracker.Infrastructure/Services/GitHubUpdateChecker.cs (3 of 5 changes were fixes)
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with MinimaxProvider.cs, DatabaseMigrationService.cs, GitHubUpdateChecker.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainWindowRuntimeLogic.cs, MainWindowRuntimeLogic.Presentation.cs, ProviderUsageProcessingPipeline.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.1 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
45 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is AIUsageTracker.UI.Slim/SettingsWindow.Providers.cs. Counted over 135 of the 311 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Small-team knowledge concentration
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 48 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (48). — One of this dimension's main actionable groups (48 issue-level).
Resolve the 6 NoWarnInCsproj finding(s) in Explicit Debt — start with AIUsageTracker.Monitor.Tests.csproj (2), AIUsageTracker.Web.Tests.csproj (2), AIUsageTracker.Tests.csproj. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PowerStateListener.cs, GeminiProviderTests.cs, ThemeApplicationTests.cs. — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
10 projects, 491 source files, 67224 hand-written lines of code (37095 production / 30129 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), 17 inter-project edges.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 6 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×3AIUsageTracker.Core/Utilities/ResetTimeParser.cs:192
What to do
Resolve the 14 redundant comment finding(s) in Comment Value — start with ClaudeCodeProvider.cs (2), Program.cs, MonitorJobSchedulerTests.cs. — One of this dimension's main actionable groups (14 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
85 % of calls cross a namespace and 2 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
8 finding(s): 0 critical, 8 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
Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
13 finding(s): 0 critical, 12 high, 1 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 19 file(s) — `AIUsageTracker.Infrastructure/Configuration/AtomicFileWriter.cs` (lines 9–66, lines 68–71, line 75, …), `AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs` (line 290), `AIUsageTracker.Monitor.Tests/MonitorJobSchedulerTests.cs` (line 200, line 201), `AIUsageTracker.Monitor.Tests/ProviderConnectivityCheckServiceTests.cs` (line 34, line 62, line 109), `AIUsageTracker.Monitor.Tests/ProviderRefreshNotificationServiceTests.cs` (line 156, line 168), … (+14 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 4 of those file(s) — `AIUsageTracker.Tests/Services/UsageDatabaseCircuitBreakerTests.cs`, `AIUsageTracker.Tests/Services/UsageDatabaseDedupTests.cs`, `AIUsageTracker.Tests/Services/UsageDatabasePipelineTests.cs`, `AIUsageTracker.Tests/Services/UsageDatabaseReadTests.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 3 of those file(s) — `AIUsageTracker.Infrastructure/Configuration/AtomicFileWriter.cs`, `AIUsageTracker.Monitor/Services/MonitorJobScheduler.cs`, `AIUsageTracker.Tests/Services/UsageDatabaseCircuitBreakerTests.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
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).
No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 135 of the 311 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
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 <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×3) — AIUsageTracker.Web/Pages/Analytics.cshtml:90, AIUsageTracker.Web/Pages/Analytics.cshtml:102, AIUsageTracker.Web/Pages/Charts.cshtml:40
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.
Do you agree with this assessment?
AC2 · Forms & labels5.6 / 10Adequate✓ 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. (×3) — AIUsageTracker.Web/Pages/Analytics.cshtml:19, AIUsageTracker.Web/Pages/Charts.cshtml:18, AIUsageTracker.Web/Pages/Shared/_Layout.cshtml:77
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.
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.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — AIUsageTracker.Web/Pages/DataView.cshtml:12, AIUsageTracker.Web/Pages/Index.cshtml:24
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.
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".
A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — AIUsageTracker.Web/Pages/Shared/_Layout.cshtml:121
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
`.nav-link.active` sets color: #8839ef on background-color: #e6e9ef — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — AIUsageTracker.Web/wwwroot/css/themes.css:315
`.btn` moves (`transition: transform 0.15s ease, background-color 0.15s 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. — docs/landing/style.css:50
`.screenshot-item img` moves (`transition: transform 0.2s ease, border-color 0.2s 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. — docs/landing/style.css:291
`.support-card` moves (`transition: border-color 0.15s ease, transform 0.15s 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. — docs/landing/style.css:364
`.reliability-card` moves (`transition: transform 0.2s ease, box-shadow 0.2s 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. — AIUsageTracker.Web/wwwroot/css/site.css:88
`.reliability-progress-bar` moves (`transition: width 0.3s 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. — AIUsageTracker.Web/wwwroot/css/site.css:167
`.progress-bar-fill` moves (`transition: width 0.2s`) 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. — AIUsageTracker.Web/wwwroot/css/site.css:300
`.budget-progress-bar` moves (`transition: width 0.3s 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. — AIUsageTracker.Web/wwwroot/css/site.css:512
`.distribution-fill` moves (`transition: width 0.3s 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. — AIUsageTracker.Web/wwwroot/css/site.css:785
`.sidebar` moves (`transition: transform 0.2s`) 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. — AIUsageTracker.Web/wwwroot/css/themes.css:454
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.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`MonitorService` is a singleton (one shared instance) but mutates instance state outside any lock (AgentUrl, LastAgentErrors, _usageRequestCount, _usageTotalLatencyMs, _usageLastLatencyMs, _usageErrorCount; e.g. `AgentUrl` at line 139). — AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:18
`WindowsNotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_isInitialized; e.g. `_isInitialized` at line 35). — AIUsageTracker.Infrastructure/Services/WindowsNotificationService.cs:11
`GitHubAuthService` is a singleton (one shared instance) but mutates instance state outside any lock (_currentToken, _cliTokenLookupAttempted, _cachedUsername; e.g. `_currentToken` at line 127). — AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:15
`MonitorJobScheduler` is a singleton (one shared instance) but mutates instance state outside any lock (_schedulerToken, _lastDequeuedPriority, _maxObservedQueueWaitMs, _dispatchPatternIndex; e.g. `_schedulerToken` at line 244). — AIUsageTracker.Monitor/Services/MonitorJobScheduler.cs:10
`ProviderManagerLifecycleService` is a singleton (one shared instance) but mutates instance state outside any lock (CurrentMaxConcurrency; e.g. `CurrentMaxConcurrency` at line 74). — AIUsageTracker.Monitor/Services/ProviderManagerLifecycleService.cs:11
`ProviderRefreshNotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_lastUsageHash; e.g. `_lastUsageHash` at line 51). — AIUsageTracker.Monitor/Services/ProviderRefreshNotificationService.cs:14
`PowerStateListener` is a singleton (one shared instance) but mutates instance state outside any lock (_subscribedToPowerEvents; e.g. `_subscribedToPowerEvents` at line 90). — AIUsageTracker.Monitor/Services/PowerStateListener.cs:9
`MainViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (IsLoading, StatusMessage, LastRefreshTime, IsPrivacyMode; e.g. `IsLoading` at line 78). — AIUsageTracker.UI.Slim/ViewModels/MainViewModel.cs:18
`MainWindow` is a singleton (one shared instance) but mutates instance state outside any lock (_isLoading, _pollingTimer, _isPollingInProgress, _lastRefreshTrigger, _isTrayIconUpdateInProgress, _lastTrayConfigRefresh; e.g. `_isLoading` at line 24). This type is a UI view, so it is thread-CONFINED rather than locked: if every one of those mutations is reached only from the UI thread — directly, or marshalled back through the dispatcher — the confinement IS the synchronisation and there is nothing to add (do not take a lock on a view; that is how the UI thread deadlocks). Check the ones that are not: a handler for a background event that mutates before it marshals is a real race. — AIUsageTracker.UI.Slim/MainWindow.Polling.cs:13
`PreferencesStore` is a singleton (one shared instance) but mutates instance state outside any lock (_preferencesPathOverride; e.g. `_preferencesPathOverride` at line 91). — AIUsageTracker.Infrastructure/Configuration/PreferencesStore.cs:16
`AppPreferences` is not registered, but the singleton `MainWindow` creates it and keeps it in `_preferences`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (ShowUsedPercentages; e.g. `ShowUsedPercentages` at line 220). — AIUsageTracker.Core/Models/AppPreferences.cs:10
`ProviderDefinition` is not registered, but `AnthropicUsageProvider` creates it and keeps it in the static `StaticDefinition`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_handledProviderIdsSet; e.g. `_handledProviderIdsSet` at line 127). — AIUsageTracker.Core/Models/ProviderDefinition.cs:7
`ProviderMetadataCatalog` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_discoveryAssembly; e.g. `_discoveryAssembly` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — AIUsageTracker.Core/Providers/ProviderMetadataCatalog.cs:13
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
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 AIUsageTracker.UI.Slim ↔ AIUsageTracker.UI.Slim.Services ↔ AIUsageTracker.UI.Slim.ViewModels depend on each other. The lightest dependency in the cycle is AIUsageTracker.UI.Slim → AIUsageTracker.UI.Slim.ViewModels (AIUsageTracker.UI.Slim.MainWindow → AIUsageTracker.UI.Slim.ViewModels.MainViewModel, 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. — AIUsageTracker.UI.Slim/MainWindow.Polling.cs:13
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.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`IMonitorService` declares 26 members: `AgentUrl`, `LastAgentErrors`, `RefreshAgentInfoAsync`, `RefreshPortAsync`, `GetUsageAsync`, `GetGroupedUsageAsync`, `GetUsageByProviderAsync`, `GetHistoryAsync`, `GetHistoryByProviderAsync`, `TriggerRefreshAsync`, `GetConfigsAsync`, `SaveConfigAsync`, `RemoveConfigAsync`, `InvalidateGroupedUsageCache`, `SendTestNotificationAsync`, `SendTestNotificationDetailedAsync`, `ScanForKeysAsync`, `CheckProviderAsync`, `TestProviderConnectionAsync`, `CheckHealthAsync`, `CheckHealthAsync`, `GetHealthSnapshotAsync`, `CheckApiContractAsync`, `ExportDataAsync`, `ExportDataAsync`, `GetDiagnosticsSnapshotAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 26 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — AIUsageTracker.Core/Interfaces/IMonitorService.cs:10
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
`MapGet(MonitorApiRoutes.Config)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:16
`MapPost(MonitorApiRoutes.Config)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:23
`MapDelete(MonitorApiRoutes.ConfigByProviderTemplate)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:49
`MapPost(MonitorApiRoutes.ScanKeys)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:61
`MapGet(MonitorApiRoutes.Health)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorDiagnosticsEndpoints.cs:40
`MapGet(MonitorApiRoutes.Diagnostics)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorDiagnosticsEndpoints.cs:58
`MapGet(MonitorApiRoutes.History)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorHistoryEndpoints.cs:19
`MapGet(MonitorApiRoutes.HistoryByProviderTemplate)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorHistoryEndpoints.cs:27
`MapGet(MonitorApiRoutes.ResetsByProviderTemplate)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorHistoryEndpoints.cs:40
`MapPost(MonitorApiRoutes.ProviderTestTemplate)` 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:21
`MapGet(MonitorApiRoutes.Usage)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:29
`MapGet(MonitorApiRoutes.UsageGrouped)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:45
`MapGet(MonitorApiRoutes.UsageByProviderTemplate)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:70
`MapPost(MonitorApiRoutes.Refresh)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:86
`MapPost(MonitorApiRoutes.NotificationTest)` 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. — AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:109
`MapGet($"{routePrefix}/status")` 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. — AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:15
`MapPost($"{routePrefix}/start")` 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. — AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:16
`MapPost($"{routePrefix}/stop")` 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. — AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:17
`MapGet("/api/export/csv")` 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. — AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:22
`MapGet("/api/export/json")` 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. — AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:23
`MapGet("/api/export/backup")` 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. — AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:24
What to do
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
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.
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.
`GetBudgetStatusesAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — AIUsageTracker.Core/Services/UsageAnalyticsService.cs:140
`GetUsageComparisonsAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — AIUsageTracker.Core/Services/UsageAnalyticsService.cs:145
A test is skipped ("GetCurrentToken falls through to hosts.yml/gh CLI which may have real tokens on this machine") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — AIUsageTracker.Tests/Infrastructure/GitHubAuthServiceTests.cs:93
A test is skipped ("GetUsernameAsync falls through to hosts.yml which may have real usernames on this machine") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — AIUsageTracker.Tests/Infrastructure/GitHubAuthServiceTests.cs:215
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
README.md links to `MONITORS.md`, but `MONITORS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:28
docs/AGENTS.md names .NET 8, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/AGENTS.md:97
docs/ARCHITECTURE.md names .NET 8, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ARCHITECTURE.md:14
docs/superpowers/specs/2026-06-14-providerusage-shape-contract-design.md names .NET 7, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/superpowers/specs/2026-06-14-providerusage-shape-contract-design.md:74
What to do
Reconcile the README with reality: README.md links to `MONITORS.md`, but `MONITORS.md` does not exist; docs/AGENTS.md names .NET 8, but the projects target .NET 10; docs/ARCHITECTURE.md names .NET 8, but the projects target .NET 10; docs/superpowers/specs/2026-06-14-providerusage-shape-contract-design.md names .NET 7, but the projects target .NET 10.
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.
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. — .github/workflows/publish.yml:186
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — AIUsageTracker.CLI/Program.cs:71
`services.AddHttpClient(string.Empty)` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — AIUsageTracker.Infrastructure/Extensions/HttpClientExtensions.cs:14
`services.AddHttpClient("PlainClient")` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — AIUsageTracker.Infrastructure/Extensions/HttpClientExtensions.cs:17
`builder.Services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — AIUsageTracker.Monitor/Program.cs:376
What to do
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead. (×3) — AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:183, AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:310, AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:343
What to do
Move each table the code creates at runtime into the versioned migrations the repository already applies.
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 each language's code 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.
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.
`https://cdn.jsdelivr.net/npm/chart.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 3 such include(s) across the repository's markup. — AIUsageTracker.Web/Pages/Analytics.cshtml:157
Set: Content-Security-Policy. Missing: Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.5 on this card.) — AIUsageTracker.Web/Services/WebApplicationPipelineExtensions.cs:64
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Add Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
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.
`WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`). (×2) — AIUsageTracker.Infrastructure/MonitorClient/MonitorLauncher.cs:179, AIUsageTracker.Monitor/Program.cs:258
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×31) — AIUsageTracker.UI.Slim/App.xaml.cs:96, AIUsageTracker.UI.Slim/App.xaml.cs:157, AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:227, …
`SingleInstanceLockService.TryAcquire` is a synchronous helper that blocks (`WaitHandle.WaitOne`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll). — AIUsageTracker.UI.Slim/App.xaml.cs:101
What to do
Blocking `WaitHandle.WaitOne` inside an `async` method
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · 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.
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.
`ProviderRefreshService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_refreshSemaphore` itself (line 30), which makes that instance its own. But `_refreshSemaphore` is named in none of the methods the disposal search covered: `Dispose` (line 461) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_refreshSemaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — AIUsageTracker.Monitor/Services/ProviderRefreshService.cs:30
`reader` is a `FileSvgReader`, which implements `IDisposable`, and it is created here (line 65). Every use of it in `CreateIcon` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw. — AIUsageTracker.UI.Slim/Services/WpfProviderIconService.cs:65
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether 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 41/333 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×39) — AIUsageTracker.CLI/Program.cs:80, AIUsageTracker.CLI/Program.cs:168, AIUsageTracker.CLI/Program.cs:196, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — 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)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`. In Rust, where a guard or permit releases when it is dropped, whether a release written BY HAND — `add_permits` after a forgotten permit, `force_unlock` after a leaked guard, a raw lock's `unlock` — matches the state the function's own acquisitions put the primitive in: not after a try or timed acquire whose failure does not leave, not from a cleanup set up before an acquire that can fail, not skipped by a `?`, `return`, `break` or `continue`, and not on top of a guard that still releases itself.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`LogDebug` at line 120 is called with an argument built by `string.Join( ", ", allBuckets.Select(bucket => { var modelId = TryGetModelId(bucket) ?? "unknown-model"; var remainin...` (line 124), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — REDACTED:120
`LogDebug` at line 34 is called with an argument built by `string.Join(", ", usage.Select(u => u.ProviderId))` (line 37), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:34
`LogDebug` at line 77 is called with an argument built by `string.Join(", ", this._providers.Select(provider => provider.ProviderId))` (line 81), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — AIUsageTracker.Monitor/Services/ProviderManagerLifecycleService.cs:77
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped2.0 / 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.
`System.Text.Json.JsonSerializer.Serialize(Model.LatencyData ?? new List<AIUsageTracker.Core.Models.LatencyDataPoint>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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. — AIUsageTracker.Web/Pages/Analytics.cshtml:159
`System.Text.Json.JsonSerializer.Serialize(Model.HttpStatusData ?? new List<AIUsageTracker.Core.Models.HttpStatusHistoryPoint>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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. — AIUsageTracker.Web/Pages/Analytics.cshtml:160
`System.Text.Json.JsonSerializer.Serialize(Model.ChartData ?? new List<AIUsageTracker.Core.Models.ChartDataPoint>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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. — AIUsageTracker.Web/Pages/Charts.cshtml:54
`System.Text.Json.JsonSerializer.Serialize(Model.ProviderColors ?? new Dictionary<string, string>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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. — AIUsageTracker.Web/Pages/Charts.cshtml:55
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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. — AIUsageTracker.Infrastructure/MonitorClient/MonitorLauncher.cs:231
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×24) — REDACTED:25, REDACTED:30, REDACTED:42, …
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.4 `!` suppressions per 1k syntax nodes — 74 suppression(s) across the 190218 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
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).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 5 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 8 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 36 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — The runtime tier booted this repository's service, but the service booted and answers HTTP at http://127.0.0.1:5000, but serves no HTML page — nothing for the accessibility crawl. This repository also has a user interface (10 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — Test reliability not measured — no test run produced results
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 — None of 5 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D30 Dependency Vulnerabilities — 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
D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D8 Code Coverage — Coverage not measured
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 event handler(s); a message-bus package
ED5 Idempotency — 2 mutating command handler(s)/consumer(s) detected and 2 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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 — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X6 Hand-rolled structured-format parsing — 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.
AnalyzerSeverityNone .editorconfig:82— SA1309 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:83— SA1633 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:84— SA1200 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:104— VSTHRD111 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:108— VSTHRD111 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:112— VSTHRD111 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:105— CA1031 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:109— CA1031 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:113— CA1031 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:119— MA0048 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:151— MA0048 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:120— SA1649 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:131— SA1600 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:132— SA1601 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:133— SA1602 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:134— SA1604 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:135— SA1611 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:136— SA1616 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:137— SA1618 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:138— SA1651 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:139— SA1201 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:140— SA1202 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:141— SA1204 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:142— SA1214 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:143— SA1117 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
NoWarnInCsproj AIUsageTracker.Monitor.Tests/AIUsageTracker.Monitor.Tests.csproj:8— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj AIUsageTracker.Tests/AIUsageTracker.Tests.csproj:8— CS0618 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj AIUsageTracker.Monitor.Tests/AIUsageTracker.Monitor.Tests.csproj:8— VSTHRD111 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj AIUsageTracker.Web.Tests/AIUsageTracker.Web.Tests.csproj:9— VSTHRD111 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj AIUsageTracker.Web.Tests/AIUsageTracker.Web.Tests.csproj:9— CA1031 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj Directory.Build.props:9— 1516 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
AC2 · Forms & labels· <select> without a programmatic label · ×3
<select> without a programmatic label AIUsageTracker.Web/Pages/Analytics.cshtml:19— 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 AIUsageTracker.Web/Pages/Charts.cshtml:18— 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 AIUsageTracker.Web/Pages/Shared/_Layout.cshtml:77— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
WriteOnlyPrivateField AIUsageTracker.Monitor/Services/PowerStateListener.cs:12— private IAppPathProvider _pathProvider — 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 AIUsageTracker.Tests/Infrastructure/Providers/GeminiProviderTests.cs:18— private GeminiProvider _provider — 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 AIUsageTracker.Tests/UI/ThemeApplicationTests.cs:20— private TimeSpan StaTestTimeout — 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> AIUsageTracker.Web/Pages/Shared/_Layout.cshtml:121— A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Namespace dependency cycle AIUsageTracker.UI.Slim/MainWindow.Polling.cs:13— The namespaces AIUsageTracker.UI.Slim ↔ AIUsageTracker.UI.Slim.Services ↔ AIUsageTracker.UI.Slim.ViewModels depend on each other. The lightest dependency in the cycle is AIUsageTracker.UI.Slim → AIUsageTracker.UI.Slim.ViewModels (AIUsageTracker.UI.Slim.MainWindow → AIUsageTracker.UI.Slim.ViewModels.MainViewModel, 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.
EmptyCatchBlock AIUsageTracker.Infrastructure/MonitorClient/MonitorLauncher.cs:231— 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.
FileScopedPragmaDisable AIUsageTracker.Tests/Infrastructure/Providers/CodexProviderTests.cs:11— #pragma warning disable CS0618 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
X2 · Cancellation propagation· Async method without CancellationToken · ×39
Async method without CancellationToken: RunAsync AIUsageTracker.CLI/Program.cs:80— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleSetKeyAsync AIUsageTracker.CLI/Program.cs:168— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleConfigCommandAsync AIUsageTracker.CLI/Program.cs:196— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckProviderAsync AIUsageTracker.CLI/Program.cs:212— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CheckSingleProviderAsync AIUsageTracker.CLI/Program.cs:229— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExportDataAsync AIUsageTracker.CLI/Program.cs:247— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowHistoryAsync AIUsageTracker.CLI/Program.cs:296— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SetKeyAsync AIUsageTracker.CLI/Program.cs:333— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RemoveKeyAsync AIUsageTracker.CLI/Program.cs:373— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ScanKeysAsync AIUsageTracker.CLI/Program.cs:387— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowConfigAsync AIUsageTracker.CLI/Program.cs:409— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SetConfigAsync AIUsageTracker.CLI/Program.cs:417— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ManageAgentAsync AIUsageTracker.CLI/Program.cs:466— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowStatusAsync AIUsageTracker.CLI/Program.cs:520— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowListAsync AIUsageTracker.CLI/Program.cs:597— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetConfigsAsync AIUsageTracker.Core/Services/ProviderManager.cs:61— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetBurnRateForecastsAsync AIUsageTracker.Core/Services/UsageAnalyticsService.cs:30— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetProviderReliabilityAsync AIUsageTracker.Core/Services/UsageAnalyticsService.cs:66— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetUsageAnomaliesAsync AIUsageTracker.Core/Services/UsageAnalyticsService.cs:104— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WriteAllTextAtomicAsync AIUsageTracker.Infrastructure/Configuration/AtomicFileWriter.cs:21— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReadJsonElementMapAsync AIUsageTracker.Infrastructure/Configuration/JsonConfigFileStore.cs:15— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReadAsync AIUsageTracker.Infrastructure/Configuration/JsonConfigFileStore.cs:38— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WriteIndentedAsync AIUsageTracker.Infrastructure/Configuration/JsonConfigFileStore.cs:57— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadConfigAsync AIUsageTracker.Infrastructure/Configuration/JsonConfigLoader.cs:35— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveConfigAsync AIUsageTracker.Infrastructure/Configuration/JsonConfigLoader.cs:45— No CancellationToken parameter — this work can't be stopped early once started.
Dead code: ToUtcFromUnixSeconds AIUsageTracker.Core/Extensions/DateTimeExtensions.cs:21— Method ToUtcFromUnixSeconds — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToUtcFromUnixMilliseconds AIUsageTracker.Core/Extensions/DateTimeExtensions.cs:26— Method ToUtcFromUnixMilliseconds — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToUnixSeconds AIUsageTracker.Core/Extensions/DateTimeExtensions.cs:31— Method ToUnixSeconds — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToUnixMilliseconds AIUsageTracker.Core/Extensions/DateTimeExtensions.cs:36— Method ToUnixMilliseconds — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToIso8601 AIUsageTracker.Core/Extensions/DateTimeExtensions.cs:41— Method ToIso8601 — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsRecent AIUsageTracker.Core/Extensions/DateTimeExtensions.cs:46— Method IsRecent — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: TimeSince AIUsageTracker.Core/Extensions/DateTimeExtensions.cs:51— Method TimeSince — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: InitiateDeviceFlowAsync AIUsageTracker.Core/Interfaces/IGitHubAuthService.cs:18— Method InitiateDeviceFlowAsync — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: SendTestNotificationAsync AIUsageTracker.Core/Interfaces/IMonitorService.cs:46— Method SendTestNotificationAsync — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: Unregister AIUsageTracker.Core/Interfaces/INotificationService.cs:21— Method Unregister — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsConfig AIUsageTracker.Core/Models/AuthSource.cs:55— Method IsConfig — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToAppcastSuffix AIUsageTracker.Core/Models/UpdateChannelExtensions.cs:9— Method ToAppcastSuffix — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ToDisplayName AIUsageTracker.Core/Models/UpdateChannelExtensions.cs:19— Method ToDisplayName — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: AgentHealthSnapshot AIUsageTracker.Core/MonitorClient/AgentHealthSnapshot.cs:10— NamedType AgentHealthSnapshot — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Core, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CreateBearerPostRequest AIUsageTracker.Infrastructure/Extensions/HttpRequestBuilderExtensions.cs:57— Method CreateBearerPostRequest — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: GetAgentStatusAsync AIUsageTracker.Infrastructure/MonitorClient/MonitorLauncher.cs:89— Method GetAgentStatusAsync — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: BuildNoLimitsResult AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs:165— Method BuildNoLimitsResult — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: SelectTokenLimit AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs:209— Method SelectTokenLimit — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: NoOpDataExportService AIUsageTracker.Infrastructure/Services/NoOpDataExportService.cs:5— NamedType NoOpDataExportService — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: IsNotModified AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:147— Method IsNotModified — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Monitor, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: SetProviderActiveAsync AIUsageTracker.Monitor/Services/IUsageDatabase.cs:39— Method SetProviderActiveAsync — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Monitor, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: ProviderRefreshConfigSelection AIUsageTracker.Monitor/Services/ProviderRefreshConfigSelection.cs:9— NamedType ProviderRefreshConfigSelection — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Monitor, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: MonitorTestModuleInitializer AIUsageTracker.Monitor.Tests/MonitorTestModuleInitializer.cs:11— NamedType MonitorTestModuleInitializer — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Monitor.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CreateGeminiCliMock AIUsageTracker.Tests/Mocks/MockProviderService.cs:64— Method CreateGeminiCliMock — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
Dead code: CreateAntigravityMock AIUsageTracker.Tests/Mocks/MockProviderService.cs:76— Method CreateAntigravityMock — Roslyn's SymbolFinder walked every project the solution loads, including AIUsageTracker.Tests, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository — a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol's name, and any project the workspace could not load. This is 'no caller found by this walk', not a verdict that the symbol is unused.
async void method: OnStartup AIUsageTracker.UI.Slim/App.xaml.cs:96— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnExit AIUsageTracker.UI.Slim/App.xaml.cs:157— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: PrivacyBtn_Click AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:227— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnPollingTimerTick AIUsageTracker.UI.Slim/MainWindow.Polling.cs:98— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: UpdateBtn_Click AIUsageTracker.UI.Slim/MainWindow.Updates.cs:115— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnWindowLoaded AIUsageTracker.UI.Slim/MainWindow.xaml.cs:254— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnWindowLocationChanged AIUsageTracker.UI.Slim/MainWindow.xaml.cs:271— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnWindowSizeChanged AIUsageTracker.UI.Slim/MainWindow.xaml.cs:283— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RefreshBtn_Click AIUsageTracker.UI.Slim/MainWindow.xaml.cs:593— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SettingsBtn_Click AIUsageTracker.UI.Slim/MainWindow.xaml.cs:606— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: WebBtn_Click AIUsageTracker.UI.Slim/MainWindow.xaml.cs:682— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: PrivacyBtn_Click AIUsageTracker.UI.Slim/MainWindow.xaml.cs:704— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AlwaysOnTop_Checked AIUsageTracker.UI.Slim/MainWindow.xaml.cs:725— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowUsedToggle_Checked AIUsageTracker.UI.Slim/MainWindow.xaml.cs:753— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: MonitorToggleBtn_Click AIUsageTracker.UI.Slim/MainWindow.xaml.cs:811— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ExportCsvBtn_Click AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:14— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ExportJsonBtn_Click AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:57— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RefreshHistoryBtn_Click AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:157— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RestartMonitorBtn_Click AIUsageTracker.UI.Slim/SettingsWindow.Monitor.cs:89— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: CheckHealthBtn_Click AIUsageTracker.UI.Slim/SettingsWindow.Monitor.cs:139— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ExportDiagnosticsBtn_Click AIUsageTracker.UI.Slim/SettingsWindow.Monitor.cs:228— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SettingsWindow_Loaded AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:85— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SettingsWindow_Closing AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:340— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AutoSaveTimer_Tick AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:391— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: PrivacyBtn_Click AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:691— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:16— `MapGet(MonitorApiRoutes.Config)` 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 AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:23— `MapPost(MonitorApiRoutes.Config)` 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 AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:49— `MapDelete(MonitorApiRoutes.ConfigByProviderTemplate)` 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 AIUsageTracker.Monitor/Endpoints/MonitorConfigEndpoints.cs:61— `MapPost(MonitorApiRoutes.ScanKeys)` 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 AIUsageTracker.Monitor/Endpoints/MonitorDiagnosticsEndpoints.cs:40— `MapGet(MonitorApiRoutes.Health)` 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 AIUsageTracker.Monitor/Endpoints/MonitorDiagnosticsEndpoints.cs:58— `MapGet(MonitorApiRoutes.Diagnostics)` 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 AIUsageTracker.Monitor/Endpoints/MonitorHistoryEndpoints.cs:19— `MapGet(MonitorApiRoutes.History)` 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 AIUsageTracker.Monitor/Endpoints/MonitorHistoryEndpoints.cs:27— `MapGet(MonitorApiRoutes.HistoryByProviderTemplate)` 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 AIUsageTracker.Monitor/Endpoints/MonitorHistoryEndpoints.cs:40— `MapGet(MonitorApiRoutes.ResetsByProviderTemplate)` 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:21— `MapPost(MonitorApiRoutes.ProviderTestTemplate)` 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 AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:29— `MapGet(MonitorApiRoutes.Usage)` 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 AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:45— `MapGet(MonitorApiRoutes.UsageGrouped)` 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 AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:70— `MapGet(MonitorApiRoutes.UsageByProviderTemplate)` 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 AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:86— `MapPost(MonitorApiRoutes.Refresh)` 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 AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:109— `MapPost(MonitorApiRoutes.NotificationTest)` 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 AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:15— `MapGet($"{routePrefix}/status")` 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 AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:16— `MapPost($"{routePrefix}/start")` 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 AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:17— `MapPost($"{routePrefix}/stop")` 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 AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:22— `MapGet("/api/export/csv")` 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 AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:23— `MapGet("/api/export/json")` 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 AIUsageTracker.Web/Services/WebApiEndpointMapper.cs:24— `MapGet("/api/export/backup")` 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.
Test cannot fail: WindowDragBehavior_GetEnableDrag_ReturnsFalseByDefault AIUsageTracker.Tests/UI/Behaviors/AttachedBehaviorTests.cs:17— This test's act runs inside `RunInStaAsync` at line 133 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: WindowDragBehavior_SetEnableDrag_SetsValue AIUsageTracker.Tests/UI/Behaviors/AttachedBehaviorTests.cs:34— This test's act runs inside `RunInStaAsync` at line 133 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: CloseWindowBehavior_GetCloseOnClick_ReturnsFalseByDefault AIUsageTracker.Tests/UI/Behaviors/AttachedBehaviorTests.cs:52— This test's act runs inside `RunInStaAsync` at line 133 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: CloseWindowBehavior_SetCloseOnClick_SetsValue AIUsageTracker.Tests/UI/Behaviors/AttachedBehaviorTests.cs:69— This test's act runs inside `RunInStaAsync` at line 133 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: CloseWindowBehavior_GetHideOnClick_ReturnsFalseByDefault AIUsageTracker.Tests/UI/Behaviors/AttachedBehaviorTests.cs:87— This test's act runs inside `RunInStaAsync` at line 133 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: CloseWindowBehavior_SetHideOnClick_SetsValue AIUsageTracker.Tests/UI/Behaviors/AttachedBehaviorTests.cs:104— This test's act runs inside `RunInStaAsync` at line 133 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: OpenSettingsDialogAsync_ShowsOwnedDialog_WithoutTopmostToggleAsync AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:26— This test's act runs inside `RunInStaAsync` at line 354 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 5 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: OpenInfoDialog_UsesConfiguredDialogHost_WhenMainWindowNotVisibleAsync AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:56— This test's act runs inside `RunInStaAsync` at line 354 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 3 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: CloseSettingsDialog_DoesNotMoveWindowPositionAsync AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:83— This test's act runs inside `RunInStaAsync` at line 354 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 3 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: MainWindowAndSettingsWindow_ReflectSameShowUsedPreferenceAsync AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:121— This test's act runs inside `RunInStaAsync` at line 354 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 5 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: SettingsWindow_DisplayControlsApplyToPreferencesThroughSinglePathAsync AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:149— This test's act runs inside `RunInStaAsync` at line 354 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 9 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: OpenSettingsDialogAsync_WhenSettingsChanged_ReloadsEnablePaceAdjustmentFromStoreAsync AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:204— This test's act runs inside `RunInStaAsync` at line 354 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 5 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: Diagnostic_OnPrivacyChanged_UpdatesIsPrivacyMode_WhenCalledDirectly AIUsageTracker.Tests/UI/PrivacyButtonBehaviorTests.cs:31— This test's act runs inside `RunInStaAsync` at line 325 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 2 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: PrivacyBtn_Click_TogglesPrivacyModeOn_WhenCurrentlyOff AIUsageTracker.Tests/UI/PrivacyButtonBehaviorTests.cs:68— This test's act runs inside `RunInStaAsync` at line 325 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 5 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: PrivacyBtn_Click_TogglesPrivacyModeOff_WhenCurrentlyOn AIUsageTracker.Tests/UI/PrivacyButtonBehaviorTests.cs:109— This test's act runs inside `RunInStaAsync` at line 325 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 5 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: PrivacyBtn_Click_TogglesCorrectly_OnMultipleConsecutiveClicks AIUsageTracker.Tests/UI/PrivacyButtonBehaviorTests.cs:150— This test's act runs inside `RunInStaAsync` at line 325 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 7 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
Test cannot fail: PrivacyBtn_Click_FiresPrivacyChangedEvent AIUsageTracker.Tests/UI/PrivacyButtonBehaviorTests.cs:199— This test's act runs inside `RunInStaAsync` at line 325 of this file, which catches every exception and neither rethrows nor verifies — so the method passes whether or not the behaviour it names actually happens. The 3 assertion(s) this test does make are inside that region, and an xUnit/NUnit assertion reports by THROWING — so they are caught and discarded too, which is why nothing else here flags this test. Assert the outcome instead of catching it: `Assert.Throws<T>(() => …)` (or the framework equivalent) when a throw is the expected result, or narrow the catch to the one exception type and assert on it. A catch-all that only logs belongs in production code, not between a test and its verdict.
BarePragmaDisable AIUsageTracker.Infrastructure/Configuration/PreferencesStore.cs:43— #pragma warning disable MA0004 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Monitor.Tests/ConfigServiceExtendedTests.cs:177— #pragma warning disable MA0004 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Monitor.Tests/ProviderRefreshNotificationServiceTests.cs:52— #pragma warning disable MA0004 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable REDACTED:82— #pragma warning disable S107 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:357— #pragma warning disable S107 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.UI.Slim/MainWindow.xaml.cs:95— #pragma warning disable S107 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs:151— #pragma warning disable S107 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Tests/Core/MonitorHealthSnapshotTests.cs:14— #pragma warning disable CS0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Tests/Core/MonitorHealthSnapshotTests.cs:28— #pragma warning disable CS0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Tests/Core/MonitorHealthSnapshotTests.cs:41— #pragma warning disable CS0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Tests/Core/MonitorHealthSnapshotTests.cs:55— #pragma warning disable CS0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Tests/Core/MonitorServiceTests.cs:666— #pragma warning disable CS0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:128— #pragma warning disable SYSLIB0050 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.Tests/UI/DialogOpenBehaviorTests.cs:165— #pragma warning disable SYSLIB0050 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.UI.Slim/MainWindow.xaml.cs:161— #pragma warning disable VSTHRD101 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.UI.Slim/MainWindow.xaml.cs:228— #pragma warning disable VSTHRD100 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:1014— #pragma warning disable VSTHRD100 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×11
NuGet dependencies are not locked AIUsageTracker.CLI/AIUsageTracker.CLI.csproj:9— AIUsageTracker.CLI/AIUsageTracker.CLI.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.Core/AIUsageTracker.Core.csproj:13— AIUsageTracker.Core/AIUsageTracker.Core.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.Infrastructure/AIUsageTracker.Infrastructure.csproj:4— AIUsageTracker.Infrastructure/AIUsageTracker.Infrastructure.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.Monitor.Tests/AIUsageTracker.Monitor.Tests.csproj:12— AIUsageTracker.Monitor.Tests/AIUsageTracker.Monitor.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.Monitor/AIUsageTracker.Monitor.csproj:18— AIUsageTracker.Monitor/AIUsageTracker.Monitor.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.Tests/AIUsageTracker.Tests.csproj:12— AIUsageTracker.Tests/AIUsageTracker.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.UI.Slim/AIUsageTracker.UI.Slim.csproj:23— AIUsageTracker.UI.Slim/AIUsageTracker.UI.Slim.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.Web.Tests/AIUsageTracker.Web.Tests.csproj:17— AIUsageTracker.Web.Tests/AIUsageTracker.Web.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked AIUsageTracker.Web/AIUsageTracker.Web.csproj:13— AIUsageTracker.Web/AIUsageTracker.Web.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked Directory.Build.props:14— Directory.Build.props declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
NuGet dependencies are not locked scripts/Seeder/Seeder.csproj:10— scripts/Seeder/Seeder.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — 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.
Stateful singleton: MonitorService AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:18— `MonitorService` is a singleton (one shared instance) but mutates instance state outside any lock (AgentUrl, LastAgentErrors, _usageRequestCount, _usageTotalLatencyMs, _usageLastLatencyMs, _usageErrorCount; e.g. `AgentUrl` at line 139).
Stateful singleton: WindowsNotificationService AIUsageTracker.Infrastructure/Services/WindowsNotificationService.cs:11— `WindowsNotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_isInitialized; e.g. `_isInitialized` at line 35).
Stateful singleton: GitHubAuthService AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:15— `GitHubAuthService` is a singleton (one shared instance) but mutates instance state outside any lock (_currentToken, _cliTokenLookupAttempted, _cachedUsername; e.g. `_currentToken` at line 127).
Stateful singleton: MonitorJobScheduler AIUsageTracker.Monitor/Services/MonitorJobScheduler.cs:10— `MonitorJobScheduler` is a singleton (one shared instance) but mutates instance state outside any lock (_schedulerToken, _lastDequeuedPriority, _maxObservedQueueWaitMs, _dispatchPatternIndex; e.g. `_schedulerToken` at line 244).
Stateful singleton: ProviderManagerLifecycleService AIUsageTracker.Monitor/Services/ProviderManagerLifecycleService.cs:11— `ProviderManagerLifecycleService` is a singleton (one shared instance) but mutates instance state outside any lock (CurrentMaxConcurrency; e.g. `CurrentMaxConcurrency` at line 74).
Stateful singleton: ProviderRefreshNotificationService AIUsageTracker.Monitor/Services/ProviderRefreshNotificationService.cs:14— `ProviderRefreshNotificationService` is a singleton (one shared instance) but mutates instance state outside any lock (_lastUsageHash; e.g. `_lastUsageHash` at line 51).
Stateful singleton: PowerStateListener AIUsageTracker.Monitor/Services/PowerStateListener.cs:9— `PowerStateListener` is a singleton (one shared instance) but mutates instance state outside any lock (_subscribedToPowerEvents; e.g. `_subscribedToPowerEvents` at line 90).
Stateful singleton: MainViewModel AIUsageTracker.UI.Slim/ViewModels/MainViewModel.cs:18— `MainViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (IsLoading, StatusMessage, LastRefreshTime, IsPrivacyMode; e.g. `IsLoading` at line 78).
Stateful singleton: MainWindow AIUsageTracker.UI.Slim/MainWindow.Polling.cs:13— `MainWindow` is a singleton (one shared instance) but mutates instance state outside any lock (_isLoading, _pollingTimer, _isPollingInProgress, _lastRefreshTrigger, _isTrayIconUpdateInProgress, _lastTrayConfigRefresh; e.g. `_isLoading` at line 24). This type is a UI view, so it is thread-CONFINED rather than locked: if every one of those mutations is reached only from the UI thread — directly, or marshalled back through the dispatcher — the confinement IS the synchronisation and there is nothing to add (do not take a lock on a view; that is how the UI thread deadlocks). Check the ones that are not: a handler for a background event that mutates before it marshals is a real race.
Stateful singleton: PreferencesStore AIUsageTracker.Infrastructure/Configuration/PreferencesStore.cs:16— `PreferencesStore` is a singleton (one shared instance) but mutates instance state outside any lock (_preferencesPathOverride; e.g. `_preferencesPathOverride` at line 91).
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×9
Animation without a prefers-reduced-motion guard docs/landing/style.css:50— `.btn` moves (`transition: transform 0.15s ease, background-color 0.15s 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 docs/landing/style.css:291— `.screenshot-item img` moves (`transition: transform 0.2s ease, border-color 0.2s 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 docs/landing/style.css:364— `.support-card` moves (`transition: border-color 0.15s ease, transform 0.15s 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 AIUsageTracker.Web/wwwroot/css/site.css:88— `.reliability-card` moves (`transition: transform 0.2s ease, box-shadow 0.2s 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 AIUsageTracker.Web/wwwroot/css/site.css:167— `.reliability-progress-bar` moves (`transition: width 0.3s 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 AIUsageTracker.Web/wwwroot/css/site.css:300— `.progress-bar-fill` moves (`transition: width 0.2s`) 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 AIUsageTracker.Web/wwwroot/css/site.css:512— `.budget-progress-bar` moves (`transition: width 0.3s 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 AIUsageTracker.Web/wwwroot/css/site.css:785— `.distribution-fill` moves (`transition: width 0.3s 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 AIUsageTracker.Web/wwwroot/css/themes.css:454— `.sidebar` moves (`transition: transform 0.2s`) 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.
TooManyMethods: SettingsWindow AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs— TooManyMethods — 1867 significant lines (blank, comment-only and punctuation-only lines excluded), 123 methods, declared across 5 files: AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs (51), AIUsageTracker.UI.Slim/SettingsWindow.Providers.cs (38), AIUsageTracker.UI.Slim/SettingsWindow.Cards.cs (18), AIUsageTracker.UI.Slim/SettingsWindow.Monitor.cs (10), +1 more file(s). The bar is 30 methods; this is 93 over it, 4.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainWindow AIUsageTracker.UI.Slim/MainWindow.xaml.cs— TooManyMethods — 1122 significant lines (blank, comment-only and punctuation-only lines excluded), 79 methods, declared across 5 files: AIUsageTracker.UI.Slim/MainWindow.xaml.cs (38), AIUsageTracker.UI.Slim/MainWindow.Rendering.cs (18), AIUsageTracker.UI.Slim/MainWindow.Polling.cs (9), AIUsageTracker.UI.Slim/MainWindow.Topmost.cs (9), +1 more file(s). The bar is 30 methods; this is 49 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MonitorService AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs— TooManyMethods — 559 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UsageMath AIUsageTracker.Core/Models/UsageMath.cs— TooManyMethods — 418 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: App AIUsageTracker.UI.Slim/App.Screenshots.cs— TooManyMethods — 942 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods, declared across 4 files: AIUsageTracker.UI.Slim/App.Screenshots.cs (15), AIUsageTracker.UI.Slim/App.xaml.cs (10), AIUsageTracker.UI.Slim/App.TrayIcon.cs (8), AIUsageTracker.UI.Slim/App.Themes.cs (5). The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainWindowRuntimeLogic AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs— TooManyMethods — 645 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods, declared across 2 files: AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs (24), AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs (13). The bar is 30 methods; this is 7 over it, 1.23× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: ProviderCardRenderer AIUsageTracker.UI.Slim/ProviderCardRenderer.cs— TooManyMethods — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UsageDatabase AIUsageTracker.Monitor/Services/UsageDatabase.cs— TooManyMethods — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AntigravityProvider AIUsageTracker.Infrastructure/Providers/AntigravityProvider.cs— TooManyMethods — 501 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: AIUsageTracker.UI.Slim/SettingsWindow.Providers.cs AIUsageTracker.UI.Slim/SettingsWindow.Providers.cs— FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 168 over it, 1.34× 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: AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs— FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 167 over it, 1.33× 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: Providers/AntigravityProvider.cs AIUsageTracker.Infrastructure/Providers/AntigravityProvider.cs— FileTooLong — 601 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 101 over it, 1.20× 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: MonitorClient/MonitorService.cs AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 70 over it, 1.14× 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: AIUsageTracker.UI.Slim/MainWindow.xaml.cs AIUsageTracker.UI.Slim/MainWindow.xaml.cs— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03× 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×5
Edited copy of a member (15 corresponding lines) AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs:143— AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs:143-157 | AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs:163-177 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:692— AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:692-706 | AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:925-941 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) AIUsageTracker.Core/MonitorClient/AgentGroupedUsageValueResolver.cs:55— AIUsageTracker.Core/MonitorClient/AgentGroupedUsageValueResolver.cs:55-69 | AIUsageTracker.Core/MonitorClient/AgentGroupedUsageValueResolver.cs:117-134 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) AIUsageTracker.Core/MonitorClient/AgentGroupedUsageValueResolver.cs:74— AIUsageTracker.Core/MonitorClient/AgentGroupedUsageValueResolver.cs:74-88 | AIUsageTracker.Core/MonitorClient/AgentGroupedUsageValueResolver.cs:94-111 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) AIUsageTracker.UI.Slim/Converters/RemainingPercentageConverter.cs:18— AIUsageTracker.UI.Slim/Converters/RemainingPercentageConverter.cs:18-32 | AIUsageTracker.UI.Slim/Converters/PercentageToWidthConverter.cs:17-31 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Repeated repair: AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs:179— AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is MinimaxProvider.GetRemainsUsageAsync at line 179), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Release v2.4.6 stable: Z.AI weekly quota + privacy-mode fix + Z.AI empty-data fix (#760)”; “fix: Minimax always shows two bars (5h + Weekly), remove conditional skipping”; “fix: handle Minimax Token Plan response format with remaining_percent”; “fix: remove silent fallback in Minimax period duration calculation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-04-29..2026-07-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-29 09:52:44 +03:00' --until='2026-07-28 09:52:44 +03:00' --full-history --no-merges -- AIUsageTracker.Infrastructure/Providers/MinimaxProvider.cs`: 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.
Repeated repair: AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:33— AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is DatabaseMigrationService.RunMigrations at line 33), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Release v2.4.6 stable: Z.AI weekly quota + privacy-mode fix + Z.AI empty-data fix (#760)”; “fix: migration preserves all card columns, throws on column mismatch (v2.3.6-beta.13) (#668)”; “fix: timestamp conversion was dropping newer provider_history columns (#665)”; “fix: startup delay + card_type migration for pre-Evolve databases (#663)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-04-29..2026-07-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-29 09:52:44 +03:00' --until='2026-07-28 09:52:44 +03:00' --full-history --no-merges -- AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs`: 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.
Repeated repair: AIUsageTracker.Infrastructure/Services/GitHubUpdateChecker.cs AIUsageTracker.Infrastructure/Services/GitHubUpdateChecker.cs:228— AIUsageTracker.Infrastructure/Services/GitHubUpdateChecker.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is GitHubUpdateChecker.ParseAppVersion at line 228), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Cycle 23 Core: Move ProviderMetadataCatalog to Core + fix BetaUpdateCheck suffix (#677)”; “Fix IsNewerVersion for -develop suffix in prerelease tags”; “fix: add correlated update diagnostics and persisted attempt summary”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-04-29..2026-07-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-29 09:52:44 +03:00' --until='2026-07-28 09:52:44 +03:00' --full-history --no-merges -- AIUsageTracker.Infrastructure/Services/GitHubUpdateChecker.cs`: 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.
Repeated repair: AIUsageTracker.Web/Services/WebProviderUsageMapper.cs AIUsageTracker.Web/Services/WebProviderUsageMapper.cs:68— AIUsageTracker.Web/Services/WebProviderUsageMapper.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is WebProviderUsageMapper.ParseDateTimeUtc at line 68), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Release v2.4.6 stable: Z.AI weekly quota + privacy-mode fix + Z.AI empty-data fix (#760)”; “fix: tooltip percentage respects Show Used toggle (#709)”; “fix: reconstruct ProviderUsage subtypes on DB read and preserve StatusProviderUsage through pipeline (#654)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-04-29..2026-07-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-29 09:52:44 +03:00' --until='2026-07-28 09:52:44 +03:00' --full-history --no-merges -- AIUsageTracker.Web/Services/WebProviderUsageMapper.cs`: 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.
Outbound HTTP without resilience AIUsageTracker.CLI/Program.cs:71— `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience AIUsageTracker.Infrastructure/Extensions/HttpClientExtensions.cs:14— `services.AddHttpClient(string.Empty)` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience AIUsageTracker.Infrastructure/Extensions/HttpClientExtensions.cs:17— `services.AddHttpClient("PlainClient")` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience AIUsageTracker.Monitor/Program.cs:376— `builder.Services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped AIUsageTracker.Web/Pages/Analytics.cshtml:159— `System.Text.Json.JsonSerializer.Serialize(Model.LatencyData ?? new List<AIUsageTracker.Core.Models.LatencyDataPoint>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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 AIUsageTracker.Web/Pages/Analytics.cshtml:160— `System.Text.Json.JsonSerializer.Serialize(Model.HttpStatusData ?? new List<AIUsageTracker.Core.Models.HttpStatusHistoryPoint>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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 AIUsageTracker.Web/Pages/Charts.cshtml:54— `System.Text.Json.JsonSerializer.Serialize(Model.ChartData ?? new List<AIUsageTracker.Core.Models.ChartDataPoint>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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 AIUsageTracker.Web/Pages/Charts.cshtml:55— `System.Text.Json.JsonSerializer.Serialize(Model.ProviderColors ?? new Dictionary<string, string>())` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` 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.
AC1 · Text alternatives· <canvas> without a text alternative · ×3
<canvas> without a text alternative AIUsageTracker.Web/Pages/Analytics.cshtml:90— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative AIUsageTracker.Web/Pages/Analytics.cshtml:102— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
<canvas> without a text alternative AIUsageTracker.Web/Pages/Charts.cshtml:40— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
Deprecated: xunit AIUsageTracker.Monitor.Tests/AIUsageTracker.Monitor.Tests.csproj:15— xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: xunit AIUsageTracker.Tests/AIUsageTracker.Tests.csproj:15— xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Hotspot: AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs:343— AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in MainWindowRuntimeLogic.BuildTooltipContent at line 343. 8 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-29..2026-07-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-29 09:52:44 +03:00' --until='2026-07-28 09:52:44 +03:00' --full-history --no-merges -- AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs`: 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.
Hotspot: AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs:44— AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in MainWindowRuntimeLogic.Create at line 44. 4 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-29..2026-07-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-29 09:52:44 +03:00' --until='2026-07-28 09:52:44 +03:00' --full-history --no-merges -- AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs`: 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.
Hotspot: AIUsageTracker.Monitor/Services/ProviderUsageProcessingPipeline.cs AIUsageTracker.Monitor/Services/ProviderUsageProcessingPipeline.cs:212— AIUsageTracker.Monitor/Services/ProviderUsageProcessingPipeline.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in ProviderUsageProcessingPipeline.NormalizeUsage at line 212. 3 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-04-29..2026-07-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-29 09:52:44 +03:00' --until='2026-07-28 09:52:44 +03:00' --full-history --no-merges -- AIUsageTracker.Monitor/Services/ProviderUsageProcessingPipeline.cs`: 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.
ShadowedAnalyzerSeverity .editorconfig:46— MA0016 severity is set to warning here and to none at line 150 of the same [*.cs] section — EditorConfig takes the last assignment, so this line has no effect. — the configuration and the build disagree here, and the build is right. A reader auditing this file sees the severity on THIS line and concludes the rule is configured that way; nothing on the line says it was overridden further down, so the elevation reads as policy while the override is what ships. Decide which was meant: if this severity is the real decision, move it below the later entry or delete that one, so the file says what the build does; if the later entry is the real decision, delete this line — it is not a weaker version of the policy, it is no policy at all.
ShadowedAnalyzerSeverity .editorconfig:50— MA0048 severity is set to warning here and to none at line 151 of the same [*.cs] section — EditorConfig takes the last assignment, so this line has no effect. — the configuration and the build disagree here, and the build is right. A reader auditing this file sees the severity on THIS line and concludes the rule is configured that way; nothing on the line says it was overridden further down, so the elevation reads as policy while the override is what ships. Decide which was meant: if this severity is the real decision, move it below the later entry or delete that one, so the file says what the build does; if the later entry is the real decision, delete this line — it is not a weaker version of the policy, it is no policy at all.
ShadowedAnalyzerSeverity .editorconfig:51— MA0051 severity is set to suggestion here and to none at line 152 of the same [*.cs] section — EditorConfig takes the last assignment, so this line has no effect. — the configuration and the build disagree here, and the build is right. A reader auditing this file sees the severity on THIS line and concludes the rule is configured that way; nothing on the line says it was overridden further down, so the elevation reads as policy while the override is what ships. Decide which was meant: if this severity is the real decision, move it below the later entry or delete that one, so the file says what the build does; if the later entry is the real decision, delete this line — it is not a weaker version of the policy, it is no policy at all.
MethodTooLong: CardCatalogPermutations.BuildPermutations AIUsageTracker.UI.Slim/CardCatalogPermutations.cs:52— MethodTooLong — BuildPermutations runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainWindowRuntimeLogic.TryCreateSpecialPresentation AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs:152— MethodTooLong — TryCreateSpecialPresentation runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GroqProvider.GetUsageAsync AIUsageTracker.Infrastructure/Providers/GroqProvider.cs:41— MethodTooLong — GetUsageAsync runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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· Edited copy of a member (26 corresponding lines) · ×3
Edited copy of a member (26 corresponding lines) AIUsageTracker.Infrastructure/Configuration/TokenDiscoveryService.cs:243— AIUsageTracker.Infrastructure/Configuration/TokenDiscoveryService.cs:243-268 | AIUsageTracker.Infrastructure/Configuration/TokenDiscoveryService.cs:271-301 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:517— AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:517-542 | AIUsageTracker.Infrastructure/Services/CodexAuthService.cs:51-76 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (26 corresponding lines) AIUsageTracker.Infrastructure/Configuration/TokenDiscoveryService.cs:171— AIUsageTracker.Infrastructure/Configuration/TokenDiscoveryService.cs:171-197 | AIUsageTracker.Infrastructure/Configuration/TokenDiscoveryService.cs:367-392 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:185— AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:185-198 | AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:201-214 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:545— AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:545-558 | AIUsageTracker.Infrastructure/Services/CodexAuthService.cs:79-92 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:231— AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:231-248 | REDACTED:38-51 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) AIUsageTracker.UI.Slim/MainWindow.xaml.cs:541— AIUsageTracker.UI.Slim/MainWindow.xaml.cs:541-562 | AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:417-428 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) AIUsageTracker.Core/Models/AuthSource.cs:64— AIUsageTracker.Core/Models/AuthSource.cs:64-75 | AIUsageTracker.Core/Models/AuthSource.cs:103-114 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) AIUsageTracker.UI.Slim/App.Screenshots.cs:214— AIUsageTracker.UI.Slim/App.Screenshots.cs:214-227 | AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:218-229 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×3
Edited copy of a member (11 corresponding lines) AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:691— AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:691-701 | AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:704-714 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) AIUsageTracker.UI.Slim/MainWindow.xaml.cs:570— AIUsageTracker.UI.Slim/MainWindow.xaml.cs:570-580 | AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:431-441 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) AIUsageTracker.Core/Models/ProviderDerivedModelSelector.cs:35— AIUsageTracker.Core/Models/ProviderDerivedModelSelector.cs:35-45 | AIUsageTracker.Core/Services/UsageAnalyticsService.cs:151-162 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
P8 · Schema migrations· Schema created by a CREATE TABLE statement outside the migrations · ×3
Schema created by a CREATE TABLE statement outside the migrations AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:183— This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead.
Schema created by a CREATE TABLE statement outside the migrations AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:310— This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead.
Schema created by a CREATE TABLE statement outside the migrations AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:343— This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×2
Heading level jumps from h1 to h3 AIUsageTracker.Web/Pages/DataView.cshtml:12— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 AIUsageTracker.Web/Pages/Index.cshtml:24— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Stateful shared instance: AppPreferences AIUsageTracker.Core/Models/AppPreferences.cs:10— `AppPreferences` is not registered, but the singleton `MainWindow` creates it and keeps it in `_preferences`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (ShowUsedPercentages; e.g. `ShowUsedPercentages` at line 220).
Stateful shared instance: ProviderDefinition AIUsageTracker.Core/Models/ProviderDefinition.cs:7— `ProviderDefinition` is not registered, but `AnthropicUsageProvider` creates it and keeps it in the static `StaticDefinition`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_handledProviderIdsSet; e.g. `_handledProviderIdsSet` at line 127).
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:366— AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:366-389 | AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:392-415 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) AIUsageTracker.UI.Slim/MainWindow.Polling.cs:99— AIUsageTracker.UI.Slim/MainWindow.Polling.cs:99-127 | AIUsageTracker.UI.Slim/MainWindow.Polling.cs:287-310 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) AIUsageTracker.Web/Pages/Index.cshtml.cs:100— AIUsageTracker.Web/Pages/Index.cshtml.cs:100-116 | AIUsageTracker.Web/Pages/Index.cshtml.cs:119-135 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) AIUsageTracker.Infrastructure/Configuration/JsonConfigFileStore.cs:18— AIUsageTracker.Infrastructure/Configuration/JsonConfigFileStore.cs:18-36 | AIUsageTracker.Infrastructure/Configuration/JsonConfigFileStore.cs:39-55 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) AIUsageTracker.Web/Services/WebDatabaseService.cs:398— AIUsageTracker.Web/Services/WebDatabaseService.cs:398-419 | AIUsageTracker.Web/Services/WebDatabaseService.cs:422-443 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) AIUsageTracker.UI.Slim/MainWindowDeterministicFixture.cs:115— AIUsageTracker.UI.Slim/MainWindowDeterministicFixture.cs:115-138 | AIUsageTracker.UI.Slim/SettingsWindowDeterministicFixture.cs:63-84 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) AIUsageTracker.Monitor/Services/ExportService.cs:73— AIUsageTracker.Monitor/Services/ExportService.cs:73-85 | AIUsageTracker.Web/Pages/History.cshtml.cs:75-87 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) AIUsageTracker.Web/Services/WebDatabaseService.cs:249— AIUsageTracker.Web/Services/WebDatabaseService.cs:249-261 | AIUsageTracker.Web/Services/WebDatabaseService.cs:375-395 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) AIUsageTracker.UI.Slim/MainWindow.xaml.cs:726— AIUsageTracker.UI.Slim/MainWindow.xaml.cs:726-751 | AIUsageTracker.UI.Slim/MainWindow.xaml.cs:754-773 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) AIUsageTracker.Web/Pages/Analytics.cshtml.cs:58— AIUsageTracker.Web/Pages/Analytics.cshtml.cs:58-77 | AIUsageTracker.Web/Pages/Charts.cshtml.cs:65-84 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×2
Edited copies of one member (3 members, 20+ corresponding lines) AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:297— AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:297-325 | AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:368-391 | AIUsageTracker.Infrastructure/Providers/OpenAIProvider.cs:237-256 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 20+ corresponding lines) scripts/Seeder/Program.cs:202— scripts/Seeder/Program.cs:202-222 | scripts/Seeder/Program.cs:225-248 | scripts/Seeder/Program.cs:251-270 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (10 lines × 2) AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs:416— AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs:416-425 | AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs:460-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:457— AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:457-466 | AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:489-498 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) AIUsageTracker.UI.Slim/MainWindow.xaml.cs:542— AIUsageTracker.UI.Slim/MainWindow.xaml.cs:542-550 | AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:418-426 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) AIUsageTracker.UI.Slim/MainWindow.Polling.cs:68— AIUsageTracker.UI.Slim/MainWindow.Polling.cs:68-76 | AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:234-242 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Hollow method — returns a constant without doing the work AIUsageTracker.Core/Services/UsageAnalyticsService.cs:140— `GetBudgetStatusesAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work AIUsageTracker.Core/Services/UsageAnalyticsService.cs:145— `GetUsageComparisonsAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P12 · CI test-gate honesty· Tests run only outside the merge gate · ×2
Tests run only outside the merge gate .github/workflows/code-coverage.yml:54— `dotnet test AIUsageTracker.Tests\AIUsageTracker.Tests.csproj --configuration Debug --no-build --collect:"XPlat Code Coverage" --logger tr…` is the only CI command that runs 893 test(s) (categories Integration; e.g. CodeGuardrailTests.ProductionCode_DoesNotUseSyncOver, CodeGuardrailTests.ProductionCode_DoesNotContainEmptyCatchBlocks), and the workflow runs only on pushes to named branches or tags — after the merge — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Tests run only outside the merge gate .github/workflows/code-coverage.yml:55— `dotnet test AIUsageTracker.Monitor.Tests\AIUsageTracker.Monitor.Tests.csproj --configuration Debug --no-build --collect:"XPlat Code Cover…` is the only CI command that runs 143 test(s) (e.g. AuthDiagnosticsSnapshotBuilderTests.Build_WhenAuthSourceUsesFilePath_ExtractsFallbackAndAgeBucket, AuthDiagnosticsSnapshotBuilderTests.Build_WhenAuthSourceIsEnvironmentVariable_UsesRuntimeBucketAndNoPath), and the workflow runs only on pushes to named branches or tags — after the merge — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
P12 · CI test-gate honesty· Changed-file filter skips the test gate for code the tests depend on · ×2
Changed-file filter skips the test gate for code the tests depend on .github/workflows/provider-contract-drift.yml:9— `paths` runs `dotnet test AIUsageTracker.Tests\AIUsageTracker.Tests.csproj --configuration Debug --no-restore --filter "FullyQualifiedName~Infrastructu…` (the tests of `AIUsageTracker.Tests/AIUsageTracker.Tests.csproj`) only when a change touches `AIUsageTracker.Infrastructure/Providers/**`, `AIUsageTracker.Tests/Infrastructure/Providers/**`, `AIUsageTracker.Tests/TestData/Providers/**`, `.github/workflows/provider-contract-drift.yml`, `.github/actions/setup-dotnet-cache/**`, but those tests are built from `AIUsageTracker.Core`, `AIUsageTracker.Infrastructure`, `AIUsageTracker.Monitor`, `AIUsageTracker.Tests`, `AIUsageTracker.Web` (e.g. `AIUsageTracker.Core/AIUsageTracker.Core.csproj`, `AIUsageTracker.Infrastructure/AIUsageTracker.Infrastructure.csproj`) — a change there merges with them not run, and no unfiltered gate runs them. List the test project and every project it references in the filter, or drop it.
Changed-file filter skips the test gate for code the tests depend on REDACTED:23— `paths` runs `dotnet test AIUsageTracker.Tests\AIUsageTracker.Tests.csproj --no-build --configuration Debug --filter "Category=Screenshot" --logger "co…` (the tests of `AIUsageTracker.Tests/AIUsageTracker.Tests.csproj`) only when a change touches `AIUsageTracker.UI.Slim/**`, `AIUsageTracker.Tests/UI/ScreenshotBaselineTests.cs`, `scripts/capture_screenshot.ps1`, `scripts/generate_screenshots.ps1`, `scripts/verify_slim_theme_smoke.ps1`, `docs/screenshot_*_privacy.png`, `REDACTED`, `.github/actions/setup-dotnet-cache/**`, but those tests are built from `AIUsageTracker.Core`, `AIUsageTracker.Infrastructure`, `AIUsageTracker.Monitor`, `AIUsageTracker.Tests`, `AIUsageTracker.Web` (e.g. `AIUsageTracker.Core/AIUsageTracker.Core.csproj`, `AIUsageTracker.Infrastructure/AIUsageTracker.Infrastructure.csproj`) — a change there merges with them not run, and no unfiltered gate runs them. List the test project and every project it references in the filter, or drop it.
Blocking `WaitHandle.WaitOne` inside an `async` method AIUsageTracker.Infrastructure/MonitorClient/MonitorLauncher.cs:179— `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).
Blocking `WaitHandle.WaitOne` inside an `async` method AIUsageTracker.Monitor/Program.cs:258— `WaitHandle.WaitOne` parks the thread until another thread signals it — inside a method that is already `async`, the wait should be awaitable (a `TaskCompletionSource`, `SemaphoreSlim.WaitAsync`, or `WaitHandle` bridged with `Task.Factory.FromAsync`).
Low contrast colour pair in CSS (4.4:1) AIUsageTracker.Web/wwwroot/css/themes.css:315— `.nav-link.active` sets color: #8839ef on background-color: #e6e9ef — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AX2 · Stateful singletons· Process-global static state · ×1
Process-global static state: ProviderMetadataCatalog AIUsageTracker.Core/Providers/ProviderMetadataCatalog.cs:13— `ProviderMetadataCatalog` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_discoveryAssembly; e.g. `_discoveryAssembly` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
MainWindowRuntimeLogic.BuildTooltipContent (cyclomatic 27) AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs:343— MainWindowRuntimeLogic.BuildTooltipContent has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProviderUsageProcessingPipeline.NormalizeUsage (cyclomatic 26) AIUsageTracker.Monitor/Services/ProviderUsageProcessingPipeline.cs:212— ProviderUsageProcessingPipeline.NormalizeUsage has cyclomatic complexity 26 (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.
MainWindowRuntimeLogic.Create (cyclomatic 18) AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.Presentation.cs:44— MainWindowRuntimeLogic.Create 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.
No assertions: RunMigrations_LegacyDatabase_CardTypeQueryWorksAfterMigration REDACTED:86— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Prerelease dependency: StyleCop.Analyzers — StyleCop.Analyzers resolves to 1.2.0-beta.556, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
MainWindowRuntimeLogic.BuildTooltipContent (cognitive 40) AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs:343— MainWindowRuntimeLogic.BuildTooltipContent has cognitive complexity 40 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UsageDatabase.GetLatestHistoryAsync (cognitive 21) AIUsageTracker.Monitor/Services/UsageDatabase.cs:648— UsageDatabase.GetLatestHistoryAsync has cognitive complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
MainWindow.AddProviderCardsWithGrouping (cognitive 20) AIUsageTracker.UI.Slim/MainWindow.Rendering.cs:252— MainWindow.AddProviderCardsWithGrouping has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodexProvider.BuildUsages (cognitive 17) AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:403— CodexProvider.BuildUsages has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GroqProvider.GetUsageAsync (cognitive 17) AIUsageTracker.Infrastructure/Providers/GroqProvider.cs:41— GroqProvider.GetUsageAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProviderUsageProcessingPipeline.NormalizeUsage (cognitive 17) AIUsageTracker.Monitor/Services/ProviderUsageProcessingPipeline.cs:212— ProviderUsageProcessingPipeline.NormalizeUsage has cognitive 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.
UsageAlertsService.CheckUsageAlerts (cognitive 17) AIUsageTracker.Monitor/Services/UsageAlertsService.cs:30— UsageAlertsService.CheckUsageAlerts has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenAIProvider.ParseOpenAiSessionWindows (cognitive 16) AIUsageTracker.Infrastructure/Providers/OpenAIProvider.cs:134— OpenAIProvider.ParseOpenAiSessionWindows has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZaiProvider.GetUsageAsync (cognitive 16) AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs:57— ZaiProvider.GetUsageAsync has cognitive complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExportService.ExportAsync (cognitive 16) AIUsageTracker.Monitor/Services/ExportService.cs:21— ExportService.ExportAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copies of one member (3 members, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) AIUsageTracker.Core/Services/UsageAnalyticsService.cs:34— AIUsageTracker.Core/Services/UsageAnalyticsService.cs:34-64 | AIUsageTracker.Core/Services/UsageAnalyticsService.cs:70-102 | AIUsageTracker.Core/Services/UsageAnalyticsService.cs:108-138 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:166— AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:166-203 | AIUsageTracker.UI.Slim/MainWindow.xaml.cs:776-809 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:15— AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:15-55 | AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:58-98 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) AIUsageTracker.Infrastructure/Providers/AntigravityProvider.cs:470— AIUsageTracker.Infrastructure/Providers/AntigravityProvider.cs:470-505 | AIUsageTracker.Infrastructure/Providers/AntigravityProvider.cs:508-550 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:593— AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:593-637 | AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:640-687 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) AIUsageTracker.Monitor/Services/ConfigService.cs:44— AIUsageTracker.Monitor/Services/ConfigService.cs:44-75 | AIUsageTracker.Monitor/Services/ConfigService.cs:140-169 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) AIUsageTracker.Web/Services/WebDatabaseService.cs:481— AIUsageTracker.Web/Services/WebDatabaseService.cs:481-509 | AIUsageTracker.Web/Services/WebProviderUsageMapper.cs:69-103 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 32+ corresponding lines) · ×1
Edited copies of one member (3 members, 32+ corresponding lines) AIUsageTracker.Monitor/Services/UsageDatabase.cs:912— AIUsageTracker.Monitor/Services/UsageDatabase.cs:912-943 | AIUsageTracker.Monitor/Services/UsageDatabase.cs:946-978 | AIUsageTracker.Monitor/Services/UsageDatabase.cs:981-1019 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 32 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) REDACTED:163— REDACTED:163-180 | REDACTED:321-341 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:232— AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:232-256 | AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:324-348 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) AIUsageTracker.Monitor/Services/UsageDatabase.cs:499— AIUsageTracker.Monitor/Services/UsageDatabase.cs:499-515 | AIUsageTracker.Monitor/Services/UsageDatabase.cs:620-646 | AIUsageTracker.Monitor/Services/UsageDatabase.cs:1046-1060 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) AIUsageTracker.Core/Models/UsageMath.cs:518— AIUsageTracker.Core/Models/UsageMath.cs:518-531 | AIUsageTracker.Core/Models/UsageMath.cs:534-547 | AIUsageTracker.Core/Models/UsageMath.cs:577-590 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (26 lines × 2) AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:30— AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:30-55 | AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:73-98 — 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 `AIUsageTracker.UI.Slim/SettingsWindow.Data.cs:30` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:367— AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:367-383 | AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:393-409 — 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 `AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:367` 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 (33 lines × 2) AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:171— AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:171-203 | AIUsageTracker.UI.Slim/MainWindow.xaml.cs:777-809 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:171` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) AIUsageTracker.Core/MonitorClient/AgentHealthSnapshot.cs:48— AIUsageTracker.Core/MonitorClient/AgentHealthSnapshot.cs:48-61 | AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:824-837 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 3) AIUsageTracker.Core/Services/UsageAnalyticsService.cs:47— AIUsageTracker.Core/Services/UsageAnalyticsService.cs:47-51 | AIUsageTracker.Core/Services/UsageAnalyticsService.cs:83-87 | AIUsageTracker.Core/Services/UsageAnalyticsService.cs:121-125 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AIUsageTracker.Core/Services/UsageAnalyticsService.cs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:45— AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:45-55 | AIUsageTracker.Infrastructure/Services/GitHubAuthService.cs:80-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) AIUsageTracker.Infrastructure/Providers/OpenAIProvider.cs:354— AIUsageTracker.Infrastructure/Providers/OpenAIProvider.cs:354-360 | AIUsageTracker.Infrastructure/Providers/OpenAIProvider.cs:377-383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:186— AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:186-193 | AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:202-209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:186` 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 (5 lines × 2) AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:523— AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:523-527 | AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:656-661 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: SettingsWindow (LCOM4 7) AIUsageTracker.UI.Slim/SettingsWindow.xaml.cs:22— SettingsWindow's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P12 · CI test-gate honesty· Coverage reaches no merge · ×1
Coverage reaches no merge .github/workflows/code-coverage.yml:58— `codecov/codecov-action` uploads coverage, but the workflow runs only on pushes to named branches or tags — after the merge: no pull request ever reports coverage for `.`, and nothing that runs on one enforces a floor — the number can fall and every change still merges. Upload (or enforce the floor) on pull requests too.
P12 · CI test-gate honesty· Test project never run by CI · ×1
Test project never run by CI AIUsageTracker.Web.Tests/AIUsageTracker.Web.Tests.csproj:1— `AIUsageTracker.Web.Tests/AIUsageTracker.Web.Tests.csproj` declares 38 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Third-party script without Subresource Integrity AIUsageTracker.Web/Pages/Analytics.cshtml:157— `https://cdn.jsdelivr.net/npm/chart.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 3 such include(s) across the repository's markup.
Blocking `SingleInstanceLockService.TryAcquire` inside an `async` method AIUsageTracker.UI.Slim/App.xaml.cs:101— `SingleInstanceLockService.TryAcquire` is a synchronous helper that blocks (`WaitHandle.WaitOne`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll).
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×1
Owned disposable field is never released AIUsageTracker.Monitor/Services/ProviderRefreshService.cs:30— `ProviderRefreshService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_refreshSemaphore` itself (line 30), which makes that instance its own. But `_refreshSemaphore` is named in none of the methods the disposal search covered: `Dispose` (line 461) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_refreshSemaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×1
Disposable created and abandoned in the method that made it AIUsageTracker.UI.Slim/Services/WpfProviderIconService.cs:65— `reader` is a `FileSvgReader`, which implements `IDisposable`, and it is created here (line 65). Every use of it in `CreateIcon` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var reader = …;`), which releases it at the end of the scope on every path including a throw.
Swallowed exception (empty catch) AIUsageTracker.Infrastructure/MonitorClient/MonitorLauncher.cs:231— 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.
Interpolated log message defeats structured logging REDACTED:25— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:30— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:42— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:53— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:64— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:72— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:77— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:178— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:282— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging REDACTED:291— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:170— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.Infrastructure/MonitorClient/MonitorService.cs:177— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Polling.cs:276— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Polling.cs:281— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Rendering.cs:30— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Rendering.cs:32— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Rendering.cs:37— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Rendering.cs:55— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Rendering.cs:84— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Topmost.cs:33— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.Topmost.cs:127— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.xaml.cs:215— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.xaml.cs:224— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging AIUsageTracker.UI.Slim/MainWindow.xaml.cs:385— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
redundant comment AIUsageTracker.CLI/Program.cs:422— "Reflection to set property" repeats the code it sits on: 3 of its 3 words (reflection, set, property) are already in `var prop = prefs.GetType().GetProperty(key, System.Reflection.BindingFlags.IgnoreCase | System.Reflection.BindingFlags.P …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Infrastructure/Providers/ClaudeCodeProvider.cs:380— "Extract rate limit information from headers" repeats the code it sits on: 4 of its 5 words (extract, rate, limit, headers) are already in `var rateLimitHeaders = ExtractRateLimitInfo(testResponse.Headers);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Infrastructure/Providers/ClaudeCodeProvider.cs:407— "Build description with rate limit info" repeats the code it sits on: 4 of its 5 words (description, rate, limit, info) are already in `var description = $"Tier: {rateLimitHeaders.GetTierName()} | RPM: {rateLimitHeaders.RequestsRemaining.ToString(CultureIn …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Monitor.Tests/MonitorJobSchedulerTests.cs:357— "Wait for first job to start" repeats the code it sits on: 4 of its 4 words (wait, first, job, start) are already in `var started = await Task.WhenAny(firstJobStarted.Task, Task.Delay(TimeSpan.FromSeconds(5))) == firstJobStarted.Task;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Tests/Infrastructure/Providers/OpenAIProviderTests.cs:107— "5h burst: 45.5% used" repeats the code it sits on: 3 of its 3 words (burst, 45, used) are already in `Assert.Equal(45.5, burstCard.UsedPercent); // 5h burst: 45.5% used`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Tests/Integration/MonitorDiResolutionTests.cs:48— "GitHub auth" repeats the code it sits on: 3 of its 3 words (git, hub, auth) are already in `services.AddSingleton<IGitHubAuthService, StubGitHubAuthService>();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Tests/Integration/ProviderResponseDeserializationTests.cs:72— "Assert — flat cards: burst, weekly" repeats the code it sits on: 5 of its 5 words (assert, flat, cards, burst, weekly) are already in `Assert.True(usages.Count >= 2, $"Expected at least 2 flat cards (burst, weekly), got {usages.Count}");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Tests/Services/GroupedUsageProjectionServiceTests.cs:15— "Antigravity emits flat cards with CardId set; BuildModelsFromFlatCards picks them up." repeats the code it sits on: 8 of its 10 words (antigravity, flat, cards, card, id, set, build, models) are already in `var usages = new[]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Tests/Services/UsageDatabaseCircuitBreakerTests.cs:129— "------------------------------------------------------------------------- Multiple providers independently circuit-break --------------------------------------- …" repeats the code it sits on: 4 of its 5 words (multiple, providers, independently, circuit) are already in `[Fact]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.Tests/Services/UsageDatabaseReadTests.cs:273— "------------------------------------------------------------------------- GetHistoryByProviderAsync — filtering ------------------------------------------------ …" repeats the code it sits on: 5 of its 5 words (get, history, provider, async, filtering) are already in `[Fact]`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.UI.Slim/Converters/PercentageToWidthConverter.cs:29— "Return as a star-based GridLength" repeats the code it sits on: 4 of its 5 words (return, star, grid, length) are already in `return new GridLength(clampedPercentage, GridUnitType.Star);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.UI.Slim/Converters/RemainingPercentageConverter.cs:30— "Return as a star-based GridLength" repeats the code it sits on: 4 of its 5 words (return, star, grid, length) are already in `return new GridLength(remaining, GridUnitType.Star);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:82— ".NET Runtime version" repeats the code it sits on: 3 of its 3 words (net, runtime, version) are already in `this.DotNetVersionText.Text = RuntimeInformation.FrameworkDescription;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment AIUsageTracker.UI.Slim/MainWindow.Polling.cs:27— "Trigger refresh on monitor" repeats the code it sits on: 3 of its 3 words (trigger, refresh, monitor) are already in `await this._monitorService.TriggerRefreshAsync().ConfigureAwait(true);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate AIUsageTracker.UI.Slim/InfoDialog.xaml.cs:178— `dashIndex < 0 || dashIndex >= normalized.Length - 1` appears character-identically in 2 files — AIUsageTracker.UI.Slim/InfoDialog.xaml.cs, AIUsageTracker.UI.Slim/MainWindow.xaml.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 AIUsageTracker.Core/Services/ProviderManager.cs:299— `includeProviderIds != null && includeProviderIds.Count > 0` appears character-identically in 2 files — AIUsageTracker.Core/Services/ProviderManager.cs, AIUsageTracker.Monitor/Services/ProviderRefreshService.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 AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs:430— `periodDuration.HasValue && periodDuration.Value.TotalDays >= 1` appears character-identically in 2 files — AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.cs, AIUsageTracker.UI.Slim/ProviderCardRenderer.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 AIUsageTracker.Infrastructure/Providers/CodexProvider.cs:284— `resetAtEpoch.HasValue && resetAtEpoch.Value > 0` appears character-identically in 2 files — AIUsageTracker.Infrastructure/Providers/CodexProvider.cs, AIUsageTracker.Infrastructure/Providers/OpenAIProvider.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 AIUsageTracker.Infrastructure/Providers/MistralProvider.cs:55— `string.IsNullOrEmpty(apiKey) && this.DiscoveryService != null` appears character-identically in 2 files — AIUsageTracker.Infrastructure/Providers/MistralProvider.cs, AIUsageTracker.Infrastructure/Providers/OpenCodeProvider.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 AIUsageTracker.Core/Providers/ProviderMetadataCatalog.cs:238— `t.IsClass && !t.IsAbstract && typeof(IProviderService).IsAssignableFrom(t)` appears character-identically in 2 files — AIUsageTracker.Core/Providers/ProviderMetadataCatalog.cs, AIUsageTracker.Infrastructure/Extensions/ProviderRegistrationExtensions.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 AIUsageTracker.Monitor/Services/UsageAlertsService.cs:252— `usage is QuotaProviderUsage q && q.IsQuotaBased` appears character-identically in 2 files — AIUsageTracker.Monitor/Services/UsageAlertsService.cs, AIUsageTracker.UI.Slim/MainWindowRuntimeLogic.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 AIUsageTracker.UI.Slim/Converters/PercentageToWidthConverter.cs:35— `value is GridLength gridLength && gridLength.IsStar` appears character-identically in 2 files — AIUsageTracker.UI.Slim/Converters/PercentageToWidthConverter.cs, AIUsageTracker.UI.Slim/Converters/RemainingPercentageConverter.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 AIUsageTracker.Monitor/Services/UsageAlertsService.cs:161— `window.Kind == WindowKind.Rolling && window.PeriodDuration.HasValue` appears character-identically in 2 files — AIUsageTracker.Monitor/Services/UsageAlertsService.cs, AIUsageTracker.UI.Slim/FlatWindowCardBuilder.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 AIUsageTracker.Monitor/Services/UsageAlertsService.cs:167— `window.PeriodDuration.HasValue && !string.IsNullOrWhiteSpace(window.ChildProviderId) && string.Equals(window.ChildProviderId, providerId, St…` appears character-identically in 2 files — AIUsageTracker.Monitor/Services/UsageAlertsService.cs, AIUsageTracker.UI.Slim/FlatWindowCardBuilder.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.
Silent fallback default on parse failure AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:179— `ExtractTokenCount` falls back to `0` when `match.Success && match.Groups.Count > 1` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:194— `ParseInt` falls back to `0` when `int.TryParse(valueText, NumberStyles.Any, CultureInfo.InvariantCulture, out var …` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure AIUsageTracker.Infrastructure/Providers/OpenCodeZenProvider.cs:210— `ParseDouble` falls back to `0` when `double.TryParse(valueText, NumberStyles.Any, CultureInfo.InvariantCulture, out v…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure AIUsageTracker.Infrastructure/Services/GitHubUpdateChecker.cs:241— `ParseAppVersion` falls back to `0` when `int.TryParse(betaNumStr, NumberStyles.Integer, CultureInfo.InvariantCulture, out…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure AIUsageTracker.Infrastructure/Services/GitHubUpdateChecker.cs:337— `TryParseRelease` falls back to `DateTime.UtcNow` when `release.TryGetProperty("published_at", out var pub) && DateTime.TryParse(pub.Get…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure AIUsageTracker.Web/Services/WebDatabaseService.cs:502— `ParseFetchedAt` falls back to `DateTime.UtcNow` when `DateTime.TryParse( Convert.ToString(value, CultureInfo.InvariantCulture), Cultur…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default in catch AIUsageTracker.Infrastructure/Providers/AntigravityProvider.cs:289— `IsAntigravityDesktopRunning` swallows `Exception` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch AIUsageTracker.Monitor/Logging/MonitorLogPathResolver.cs:56— `TryEnsureDirectory` swallows `UnauthorizedAccessException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch AIUsageTracker.Monitor/Services/DatabaseMigrationService.cs:111— `HasAppliedEvolveMigrations` swallows `SqliteException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch AIUsageTracker.UI.Slim/MainWindow.Topmost.cs:66— `GetForegroundWindowSummary` swallows `Exception` and sets `processName = "unavailable";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch AIUsageTracker.Web/Services/WebRuntimePathResolver.cs:53— `TryEnsureDirectory` swallows `UnauthorizedAccessException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
README/code drift README.md:28— README.md links to `MONITORS.md`, but `MONITORS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/AGENTS.md:97— docs/AGENTS.md names .NET 8, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ARCHITECTURE.md:14— docs/ARCHITECTURE.md names .NET 8, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/superpowers/specs/2026-06-14-providerusage-shape-contract-design.md:74— docs/superpowers/specs/2026-06-14-providerusage-shape-contract-design.md names .NET 7, but the projects target .NET 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
DuplicateAnalyzerSeverity .editorconfig:33— VSTHRD110 severity is assigned warning twice in the same [*.cs] section — here and again at line 156. The later assignment is the one that applies; this one is a duplicate to remove. — both lines say the same thing, so nothing about the build changes either way, but the repetition is what makes the next edit dangerous: whoever changes one of them will believe the change took effect, and the surviving copy will silently keep the old behaviour. Delete this one and leave a single entry for the rule.
DuplicateAnalyzerSeverity .editorconfig:43— MA0004 severity is assigned warning twice in the same [*.cs] section — here and again at line 148. The later assignment is the one that applies; this one is a duplicate to remove. — both lines say the same thing, so nothing about the build changes either way, but the repetition is what makes the next edit dangerous: whoever changes one of them will believe the change took effect, and the surviving copy will silently keep the old behaviour. Delete this one and leave a single entry for the rule.
DuplicateAnalyzerSeverity .editorconfig:44— MA0006 severity is assigned error twice in the same [*.cs] section — here and again at line 149. The later assignment is the one that applies; this one is a duplicate to remove. — both lines say the same thing, so nothing about the build changes either way, but the repetition is what makes the next edit dangerous: whoever changes one of them will believe the change took effect, and the surviving copy will silently keep the old behaviour. Delete this one and leave a single entry for the rule.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×3
Diagnostic log message is built whether or not it is wanted REDACTED:120— `LogDebug` at line 120 is called with an argument built by `string.Join( ", ", allBuckets.Select(bucket => { var modelId = TryGetModelId(bucket) ?? "unknown-model"; var remainin...` (line 124), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Diagnostic log message is built whether or not it is wanted AIUsageTracker.Monitor/Endpoints/MonitorUsageEndpoints.cs:34— `LogDebug` at line 34 is called with an argument built by `string.Join(", ", usage.Select(u => u.ProviderId))` (line 37), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Diagnostic log message is built whether or not it is wanted AIUsageTracker.Monitor/Services/ProviderManagerLifecycleService.cs:77— `LogDebug` at line 77 is called with an argument built by `string.Join(", ", this._providers.Select(provider => provider.ProviderId))` (line 81), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Pass-through layer AIUsageTracker.Infrastructure/MonitorClient/MonitorLifecycleService.cs:9— MonitorLifecycleService: all 9 public methods forward their arguments unchanged to _launcher and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _launcher directly, or give the layer a job.
Pass-through layer AIUsageTracker.Web/Services/MonitorLauncherClient.cs:10— MonitorLauncherClient: all 3 public methods forward their arguments unchanged to _monitorLauncher and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _monitorLauncher directly, or give the layer a job.
Disabled test AIUsageTracker.Tests/Infrastructure/GitHubAuthServiceTests.cs:93— A test is skipped ("GetCurrentToken falls through to hosts.yml/gh CLI which may have real tokens on this machine") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test AIUsageTracker.Tests/Infrastructure/GitHubAuthServiceTests.cs:215— A test is skipped ("GetUsernameAsync falls through to hosts.yml which may have real usernames on this machine") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Fat interface: IMonitorService (26 members) AIUsageTracker.Core/Interfaces/IMonitorService.cs:10— `IMonitorService` declares 26 members: `AgentUrl`, `LastAgentErrors`, `RefreshAgentInfoAsync`, `RefreshPortAsync`, `GetUsageAsync`, `GetGroupedUsageAsync`, `GetUsageByProviderAsync`, `GetHistoryAsync`, `GetHistoryByProviderAsync`, `TriggerRefreshAsync`, `GetConfigsAsync`, `SaveConfigAsync`, `RemoveConfigAsync`, `InvalidateGroupedUsageCache`, `SendTestNotificationAsync`, `SendTestNotificationDetailedAsync`, `ScanForKeysAsync`, `CheckProviderAsync`, `TestProviderConnectionAsync`, `CheckHealthAsync`, `CheckHealthAsync`, `GetHealthSnapshotAsync`, `CheckApiContractAsync`, `ExportDataAsync`, `ExportDataAsync`, `GetDiagnosticsSnapshotAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 26 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Outdated: Microsoft.AspNetCore.SignalR.Client AIUsageTracker.UI.Slim/AIUsageTracker.UI.Slim.csproj:31— Microsoft.AspNetCore.SignalR.Client 8.0.25 → 11.0.0 available (referenced by AIUsageTracker.UI.Slim).
D16 · Bus Factor· Small-team knowledge concentration · ×1
Small-team knowledge concentration — 45 file(s) are concentrated to one author — the ambient state with 2 active author(s), not 45 separate risks. The signal becomes meaningful as ownership spreads; no per-file action implied now.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 10 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety .github/workflows/publish.yml:186— 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.
Security headers incomplete AIUsageTracker.Web/Services/WebApplicationPipelineExtensions.cs:64— Set: Content-Security-Policy. Missing: Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−1.5 on this card.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 41/333 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.4 `!` suppressions per 1k syntax nodes — 74 suppression(s) across the 190218 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Subsumed condition operand AIUsageTracker.Core/Helpers/SessionIdentityHelper.cs:151— `lower.Contains("username", StringComparison.Ordinal)` can never decide this `||` — every value satisfying `lower.Contains("username", StringComparison.Ordinal)` also satisfies `lower.Contains("user", StringComparison.Ordinal)`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
doc comments repeat the names AIUsageTracker.Core/Utilities/ResetTimeParser.cs:192— 2 of 29 documented parameters and 0 of 117 summaries in `AIUsageTracker.Core` only repeat the member or parameter name (e.g. "The reset time." for `resetTime`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names AIUsageTracker.Tests/UI/Behaviors/AttachedBehaviorTests.cs:10— 0 of 1 documented parameters and 3 of 94 summaries in `AIUsageTracker.Tests` only repeat the member or parameter name (e.g. "Tests for attached behaviors." for `AttachedBehaviorTests`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
doc comments repeat the names AIUsageTracker.UI.Slim/Converters/PercentageToColorConverter.cs:28— 5 of 28 documented parameters and 3 of 67 summaries in `AIUsageTracker.UI.Slim` only repeat the member or parameter name (e.g. "The target type." for `targetType`). This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
Skipped (documented): GetCurrentToken_ReturnsNull_AfterLogout AIUsageTracker.Tests/Infrastructure/GitHubAuthServiceTests.cs:93— Skipped with a documented reason — a deferral, not lazy debt: GetCurrentToken falls through to hosts.yml/gh CLI which may have real tokens on this machine
Skipped (documented): GetUsernameAsync_ReturnsNull_WhenNotAuthenticated AIUsageTracker.Tests/Infrastructure/GitHubAuthServiceTests.cs:215— Skipped with a documented reason — a deferral, not lazy debt: GetUsernameAsync falls through to hosts.yml which may have real usernames on this machine
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.
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 scan
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 4 file(s) — `AIUsageTracker.Infrastructure/Configuration/AtomicFileWriter.cs`, `AIUsageTracker.Infrastructure/Providers/ZaiProvider.cs`, `AIUsageTracker.Monitor/Endpoints/MonitorDiagnosticsSnapshotFactory.cs`, `AIUsageTracker.Monitor/Services/MonitorJobScheduler.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e8fa-f441-7bac-8647-bf056cef8488 · 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 — 2 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 89 · Warnings: 330 · Recommendations: 86 · Info: 34 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 10:08 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.