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

heliosCreation/Helios-bug-tracker

Measured 21 October 2026, 22:05 UTC, at code version 3dfd3ab

Test distribution: not measuredBus factor: not measuredBoundary Type-Coupling: not measured

Test distribution is not measured: No automated tests.

Bus factor is not measured: One contributor carries this repository.

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

CAI score 29out of 100 At risk Down 2 since the last survey

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

Performance 100 Exemplary Security and Compliance 74 Adequate Architecture 73 Strong Code Health 65 Adequate Maturity 40 Weak Accessibility 30 Weak Production Readiness 12 Critical

A medium codebase: 40,944 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 12

Findings by how serious they are

72 critical 218 serious 78 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 22:05 UTC

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

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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

75of 81 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
341of 368 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
81dimensions across 7 lenses, read from 40,944 lines of product code in 5 projects.
Chapters

Executive summary

heliosCreation/Helios-bug-tracker scores 29 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

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

72 findings are critical: 40 in Forms & labels, seven in Dependency Vulnerabilities, six in Page structure, five in ARIA correctness, four in Keyboard semantics, three in Explicit Debt, two in Change Coupling, two in Dependency Hygiene, one in Code Coverage, one in Project dependency cycles and one in Secret Scanning.

Watchdog couldn't measure Navigability and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 40,944 lines, which would take an estimated 0.4 person-years, around €57,000, to rebuild.

Code Health 65 Adequate, capped by Nullable reference types Architecture 73 Strong Maturity 40 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 12 ⚠ Critical, capped by Code Coverage, Test Distribution, Dependency Hygiene, CI/CD gates, Observability and Security & performance tooling Security and Compliance 74 Adequate, capped by Dependency Vulnerabilities Accessibility 30 Weak, capped by Text alternatives and Keyboard semantics Performance 100 ★ Exemplary

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 12 · counts for 46%Accessibility 30 · counts for 25%Maturity 40 · counts for 14%Code Health 65 · counts for 8%Architecture 73 · counts for 4%Security and Compliance 74 · counts for 2%Performance 100 · counts for 1%

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

Code composition: what the lines of code are
Business logic 6%Supporting code 37%Generated by tools 57%
New since the last survey: 69 findings

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

  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore src/BugTracker.Domain/BugTracker.Domain.csproj
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.EntityFrameworkCore.Tools REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.EntityFrameworkCore.Tools REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED
  • Dependency Hygiene · Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED
  • Explicit Debt · Dead code: GetOnly src/BugTracker.Application/Contracts/Data/IAsyncRepository.cs
  • Explicit Debt · Dead code: UpdateAsync src/BugTracker.Application/Contracts/Data/IAsyncRepository.cs
  • Explicit Debt · Dead code: GetTypeName src/BugTracker.Application/Contracts/Data/ITicketConfigurationRepository.cs
  • Explicit Debt · Dead code: GetPriorityName src/BugTracker.Application/Contracts/Data/ITicketConfigurationRepository.cs
  • Explicit Debt · Dead code: GetStatusName src/BugTracker.Application/Contracts/Data/ITicketConfigurationRepository.cs
  • Explicit Debt · Dead code: AddUserToRole src/BugTracker.Application/Contracts/Identity/IIdentityService.cs
  • Explicit Debt · Dead code: RemoveUserFromRole src/BugTracker.Application/Contracts/Identity/IIdentityService.cs
  • Explicit Debt · Dead code: UsernameExist src/BugTracker.Application/Contracts/Identity/IIdentityService.cs
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Change Coupling · Boundary-crossing change coupling: TicketRepository.cs ↔ TicketController.cs src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Change Coupling · Boundary-crossing change coupling: IdentityService.cs ↔ UserController.cs src/BugTracker.Persistence/Services/Identity/IdentityService.cs
  • Cancellation propagation · Async method without CancellationToken: GetAudits src/BugTracker.Persistence/Services/Audits/AuditRepository.cs
  • Cancellation propagation · Async method without CancellationToken: ListAll src/BugTracker.Persistence/Services/Audits/AuditRepository.cs
  • Cancellation propagation · Async method without CancellationToken: CountAll src/BugTracker.Persistence/Services/Audits/AuditRepository.cs
  • Cancellation propagation · Async method without CancellationToken: AddAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs
  • Cancellation propagation · Async method without CancellationToken: DeleteAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetByIdAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetOnly src/BugTracker.Persistence/Services/Data/BaseRepository.cs
  • Cancellation propagation · Async method without CancellationToken: ListAllAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs
  • Cancellation propagation · Async method without CancellationToken: ListAllAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetByTicket src/BugTracker.Persistence/Services/Data/CommentRepository.cs
  • Cancellation propagation · Async method without CancellationToken: AddProjectAsync src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateProjectAsync src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: ListAll src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: CountProject src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectIdByTicketId src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: UserBelongsToProjectTeam src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectTeamIds src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: NameIsUnique src/BugTracker.Persistence/Services/Data/ProjectRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetPriorities src/BugTracker.Persistence/Services/Data/TicketConfigurationsRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetPriorityName src/BugTracker.Persistence/Services/Data/TicketConfigurationsRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetStatuses src/BugTracker.Persistence/Services/Data/TicketConfigurationsRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetStatusName src/BugTracker.Persistence/Services/Data/TicketConfigurationsRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetTypes src/BugTracker.Persistence/Services/Data/TicketConfigurationsRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetTypeName src/BugTracker.Persistence/Services/Data/TicketConfigurationsRepository.cs
  • Cancellation propagation · Async method without CancellationToken: CountUserAssignedTickets src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Cancellation propagation · Async method without CancellationToken: CountProjectTicket src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetDevTicketAmountByProject src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectManagerTicketCount src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetUserCreatedTicketAmount src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Cancellation propagation · Async method without CancellationToken: CountAllTickets src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Cancellation propagation · Async method without CancellationToken: GetTicketWithTeamAndConfiguration src/BugTracker.Persistence/Services/Data/TicketRepository.cs
  • Slice cohesion · Cross-slice coupling: Team → ProjectTeam src/BugTracker.Application/Features/ProjectTeam/Queries/GetAllAccessibleProjectMembers/GetAllAccessibleProjectMembersQueryHandler.cs
  • Slice cohesion · Cross-slice coupling: Projects → Tickets src/BugTracker.Application/Features/Projects/ProjectWithTicketsAndTeamVm.cs
  • Keyboard semantics · Modal dialog does not manage focus src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_modalHolderPartial.cshtml
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/WebApp/BugsTracker/wwwroot/css/auth.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/WebApp/BugsTracker/wwwroot/css/tracker.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/WebApp/BugsTracker/wwwroot/css/tracker.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/all.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/all.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/fontawesome.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/fontawesome.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/svg-with-js.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/svg-with-js.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/css/tracker.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/css/tracker.css

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

Fixed since the last survey: 70 findings

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

  • Dependency Hygiene · Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore
  • Dependency Hygiene · Deprecated: Microsoft.EntityFrameworkCore.Tools
  • Dependency Hygiene · Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions
  • Static Analysis (SAST) · Medium: REDACTED REDACTED
  • Static Analysis (SAST) · Medium: REDACTED REDACTED
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <label> that labels no control src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <label> that labels no control src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_createTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <label> that labels no control src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <label> that labels no control src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Ticket/_updateTicketModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_deleteUserManagementModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_deleteUserManagementModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_lockUserManagementModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_lockUserManagementModalPartial.cshtml
  • Forms & labels · <label> that labels no control src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_manageRoleUserManagementModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_manageRoleUserManagementModalPartial.cshtml
  • Forms & labels · <label> that labels no control src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_manageRoleUserManagementModalPartial.cshtml
  • Forms & labels · <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_manageRoleUserManagementModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_unlockUserManagementModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/UserManagement/_unlockUserManagementModalPartial.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ByUser.cshtml
  • Forms & labels · <button> with no accessible text src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ByUser.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ByUser.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ByUser.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ByUser.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ByUser.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ProjectTickets.cshtml
  • Forms & labels · <button> with no accessible text src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ProjectTickets.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ProjectTickets.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Forms & labels · <button> with no accessible text src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Forms & labels · Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Forms & labels · <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement REDACTED
Rebuild cost: about €57,000 · Estimate
Cost to rebuild€19,000 to €96,000, for 318 to 1,009 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemHigh, 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 29. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 40,944 lines of product code

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

Top priorities

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

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

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €57,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 12 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No automated tests finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 14 points for low effort, because it clears the 1 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch BugTracker BugTracker BugTracker.Application Application BugTracker->BugTracker.Application BugTracker.Infrastructure Infrastructure BugTracker->BugTracker.Infrastructure BugTracker.Persistence Persistence BugTracker->BugTracker.Persistence BugTracker.Domain Domain BugTracker.Application->BugTracker.Domain BugTracker.Infrastructure->BugTracker.Application BugTracker.Persistence->BugTracker.Application BugTracker.Persistence->BugTracker.Domain

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.

83 modules, with 175 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 43 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Application.Contracts.Infrastructure.Mail2 Application.Dto.Audits3 Application.Dto.Comments4 Application.Dto.UserManagement5 Application.Enums6 Application.Features.Projects7 Application.Responses8 Domain.Common9 Application.Contracts.Audits10 Application.ViewModel11 Domain.Identity12 Application.Contracts.Identity13 Domain.Entities14 Application.Contracts.Data15 Application.Features.Team.Queries.GetAllAccessibleMembers16 Areas.Identity.Controllers17 Persistence18 Application.Features.Audits.Queries19 Application.Features.Audits.Queries.GetAllLogs20 Application.Features.Comments.Commands.Create21 Application.Features.Comments.Queries.GetAll22 Application.Features.Projects.Commands.Create23 Application.Features.Projects.Commands.Delete24 Application.Features.Projects.Commands.Update25 Application.Features.Projects.Queries.Get26 Application.Features.Projects.Queries.GetAll27 Application.Features.Projects.Queries.GetWithTeam28 Application.Features.Projects.Queries.GetWithTickets29 Application.Features.Tickets.Commands.Create30 Application.Features.Tickets.Commands.Delete31 Application.Features.Tickets.Commands.Update32 Application.Features.Tickets.Queries.GetProjectTickets33 Application.Features.Tickets.Queries.GetTicketDiagramDataByUser34 Application.Features.Tickets.Queries.GetTicketsByUser35 Persistence.Services.Audits36 Persistence.Services.Data37 Persistence.Services.Identity38 Application.Dto.Projects39 Application.Dto.Tickets40 Areas.Tracker.Controllers
1 Application.Contracts.Infrastructure.Mail
2 Application.Dto.Audits
3 Application.Dto.Comments
4 Application.Dto.UserManagement
5 Application.Enums
6 Application.Features.Projects
7 Application.Responses
8 Domain.Common
9 Application.Contracts.Audits11
10 Application.ViewModel121
11 Domain.Identity3
12 Application.Contracts.Identity1
13 Domain.Entities32
14 Application.Contracts.Data6
15 Application.Features.Team.Queries.GetAllAccessibleMembers112
16 Areas.Identity.Controllers11
17 Persistence18
18 Application.Features.Audits.Queries211122
19 Application.Features.Audits.Queries.GetAllLogs111111
20 Application.Features.Comments.Commands.Create1113
21 Application.Features.Comments.Queries.GetAll1111
22 Application.Features.Projects.Commands.Create1112
23 Application.Features.Projects.Commands.Delete11
24 Application.Features.Projects.Commands.Update122
25 Application.Features.Projects.Queries.Get111
26 Application.Features.Projects.Queries.GetAll1111
27 Application.Features.Projects.Queries.GetWithTeam111
28 Application.Features.Projects.Queries.GetWithTickets111
29 Application.Features.Tickets.Commands.Create223
30 Application.Features.Tickets.Commands.Delete112
31 Application.Features.Tickets.Commands.Update1213
32 Application.Features.Tickets.Queries.GetProjectTickets11212
33 Application.Features.Tickets.Queries.GetTicketDiagramDataByUser11111
34 Application.Features.Tickets.Queries.GetTicketsByUser11212
35 Persistence.Services.Audits1111
36 Persistence.Services.Data2655
37 Persistence.Services.Identity111
38 Application.Dto.Projects31111
39 Application.Dto.Tickets1115111
40 Areas.Tracker.Controllers11111111
Uses a module listed above itPart of a loopThe module itself
1 Application.Contracts.Infrastructure.Mail2 Application.Dto.Audits3 Application.Dto.Comments4 Application.Dto.UserManagement5 Application.Enums6 Application.Features.Projects7 Application.Responses8 Domain.Common9 Application.Contracts.Audits10 Application.ViewModel11 Domain.Identity12 Application.Contracts.Identity13 Domain.Entities14 Application.Contracts.Data15 Application.Features.Team.Queries.GetAllAccessibleMembers16 Areas.Identity.Controllers17 Persistence18 Application.Features.Audits.Queries19 Application.Features.Audits.Queries.GetAllLogs20 Application.Features.Comments.Commands.Create21 Application.Features.Comments.Queries.GetAll22 Application.Features.Projects.Commands.Create23 Application.Features.Projects.Commands.Delete24 Application.Features.Projects.Commands.Update25 Application.Features.Projects.Queries.Get26 Application.Features.Projects.Queries.GetAll27 Application.Features.Projects.Queries.GetWithTeam28 Application.Features.Projects.Queries.GetWithTickets29 Application.Features.Tickets.Commands.Create30 Application.Features.Tickets.Commands.Delete31 Application.Features.Tickets.Commands.Update32 Application.Features.Tickets.Queries.GetProjectTickets33 Application.Features.Tickets.Queries.GetTicketDiagramDataByUser34 Application.Features.Tickets.Queries.GetTicketsByUser35 Persistence.Services.Audits36 Persistence.Services.Data37 Persistence.Services.Identity38 Application.Dto.Projects39 Application.Dto.Tickets40 Areas.Tracker.ControllersApplication.Contracts.Infrastructure.Mail1Application.Dto.Audits2Application.Dto.Comments3Application.Dto.UserManagement4Application.Enums5Application.Features.Projects6Application.Responses7Domain.Common8Application.Contracts.Audits9Application.ViewModel10Domain.Identity11Application.Contracts.Identity12Domain.Entities13Application.Contracts.Data14Application.Features.Team.Queries.GetAllAccessibleMembers15Areas.Identity.Controllers16Persistence17Application.Features.Audits.Queries18Application.Features.Audits.Queries.GetAllLogs19Application.Features.Comments.Commands.Create20Application.Features.Comments.Queries.GetAll21Application.Features.Projects.Commands.Create22Application.Features.Projects.Commands.Delete23Application.Features.Projects.Commands.Update24Application.Features.Projects.Queries.Get25Application.Features.Projects.Queries.GetAll26Application.Features.Projects.Queries.GetWithTeam27Application.Features.Projects.Queries.GetWithTickets28Application.Features.Tickets.Commands.Create29Application.Features.Tickets.Commands.Delete30Application.Features.Tickets.Commands.Update31Application.Features.Tickets.Queries.GetProjectTickets32Application.Features.Tickets.Queries.GetTicketDiagramDataByUser33Application.Features.Tickets.Queries.GetTicketsByUser34Persistence.Services.Audits35Persistence.Services.Data36Persistence.Services.Identity37Application.Dto.Projects38Application.Dto.Tickets39Areas.Tracker.Controllers401112131326112111821112211111111131111111211122111111111111122311212131121211111112121111265511131111111511111111111+43 more modules (most-connected shown)

At a glance — Code Health · 65% · Adequate · gated by X5 ·

The Good
D1 · JavaScript Cyclomatic Complexity 7.7 D4 · JavaScript Code Duplication 9.7 D17 · JavaScript Explicit Debt 8.7 D18 · JavaScript Solution Shape 10.0 D39 · JavaScript IL Efficiency 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X4 · Repo Structured logging 10.0
The Bad
D2 · JavaScript Cognitive Complexity 6.7 X2 · Repo Cancellation propagation 5.5
The Ugly
X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 73% · Strong ·

The Good
D5 · JavaScript Coupling 8.4 D6 · JavaScript Cohesion (LCOM4) 9.6 D35 · JavaScript Change Coupling 9.8 AX1 · Repo Captive dependencies 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.6 AX9 · Repo CQS / query purity 10.0
The Bad
D26 · JavaScript Project Cohesion 6.0 AX10 · Repo Code composition 5.1
The Ugly
AX7 · Repo Slice cohesion 4.9

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

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

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

The Good
D14 · JavaScript License Compliance 10.0 ED5 · Repo Idempotency 9.4 P8 · Repo Schema migrations 10.0
The Bad
D13 · JavaScript Secret Scanning 5.0
The Ugly
D8 · JavaScript Code Coverage 0.0 D12 · JavaScript Dependency Hygiene 1.5 P1 · Repo CI/CD gates 0.0 P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 74% · Adequate · gated by D30 ·

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

At a glance — Accessibility · 30% · Weak · gated by AC1, AC4 ·

The Bad
AC5 · Repo ARIA correctness 6.3 AC6 · Repo Visual & motion safety 5.1
The Ugly
AC1 · Repo Text alternatives 1.0 AC2 · Repo Forms & labels 4.0 AC3 · Repo Page structure 4.6 AC4 · Repo Keyboard semantics 2.1 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection9Medium
A03:2025 — Software Supply Chain Failures9High / Critical
A07:2025 — Authentication Failures1High / Critical

Roadmap

Immediately address the leaked secret in REDACTED and resolve the single code coverage and test distribution gaps to ensure basic quality gates are met. Concurrently, update the 12 outdated dependencies across the persistence, application, and infrastructure projects to maintain security and compatibility. Finally, remediate the 16 deprecated dependencies, prioritizing the six instances in the persistence and application project files to reduce technical debt.

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

Do thisHelpsEffortDimension
Resolve the 1 No automated tests finding(s) in Code Coverage.+13.8 ptsLowCode Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.+13.8 ptsLowTest Distribution
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+10.0 ptsLowSecret Scanning
Resolve the 2 Vulnerable finding(s) in Dependency Hygiene.+8.8 ptsLowDependency Hygiene
Resolve the 16 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6), REDACTED (6), REDACTED (2).+13.2 ptsMediumDependency Hygiene
Resolve the 12 Outdated finding(s) in Dependency Hygiene — start with REDACTED (4), REDACTED (3), REDACTED (2).+11.6 ptsMediumDependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.+3.5 ptsLowADR Quality
Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with IdentityService.cs, LogHelper.cs, TicketController.cs.+4.4 ptsMediumKnowledge Freshness

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.1SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.5SlopSecret Scanning: Leaked secret: REDACTED
REDACTED4.2MixedDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.5MixedExplicit Debt: WriteOnlyPrivateField
REDACTED4.8MixedDependency Vulnerabilities: High CVE: REDACTED
src/BugTracker.Persistence/Services/Data/TicketRepository.cs5.0MixedChange Coupling: Boundary-crossing change coupling: TicketRepository.cs ↔ TicketController.cs
src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js5.5MixedCyclomatic Complexity: Scale._computeLabelItems (cyclomatic 31)
src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js5.5MixedCyclomatic Complexity: Scale._computeLabelItems (cyclomatic 31)
src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs5.8MixedExplicit Debt: WriteOnlyPrivateField
src/BugTracker.Domain/BugTracker.Domain.csproj6.5MixedCoupling: Off the main sequence: BugTracker.Domain
src/BugTracker.Application/Contracts/Data/ITicketConfigurationRepository.cs6.9MixedExplicit Debt: Dead code: GetTypeName
src/BugTracker.Application/Contracts/Identity/IIdentityService.cs6.9MixedExplicit Debt: Dead code: AddUserToRole
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js7.0MixedCyclomatic Complexity: all.icon (cyclomatic 17)
src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js7.0MixedCyclomatic Complexity: fontawesome.icon (cyclomatic 17)
src/BugTracker.Application/Contracts/Data/IAsyncRepository.cs7.3MixedExplicit Debt: Dead code: GetOnly
src/BugTracker.Application/Features/Tickets/Queries/GetTicketsByUser/GetTicketByUserQueryHandler.cs7.6MixedExplicit Debt: WriteOnlyPrivateField
src/BugTracker.Application/Features/Projects/Commands/Create/CreateProjectCommandValidator.cs7.8MixedCode Duplication: Duplicated block (16 lines × 2)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 72

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

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

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

Could not be resolved — 7

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 75 of 81 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 81 dimensions across the health lenses
D1D2D4D5D6D8D9D12D13D14D15D17D18D19D20D21D24D26D28D29D30D34D35D39D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX3AX4AX5AX6AX7AX9C1C2C3ED5GD1IC1M1M2M3M4P1P2P3P8PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 341 of 368 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a1607f-07c3-7904-9e40-50c472320551.

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

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 26 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .js (35,357 lines, 85% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 5 deducted marker(s) and the 0.6/KLoC density on this row were taken over this repository's .NET projects ALONE: .js (35,357 lines, 85% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (42,176 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 63 further occurrence(s) are not listed individually; the score already reflects all 103.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (src/WebApp/BugsTracker). the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: share/dotnet The following frameworks were found: 6.0.36 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 7.0.20 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 8.0.27 at [/usr/sha…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project).
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 80 further occurrence(s) are not listed individually; the score already reflects all 120.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity7.7 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

19 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Scale._computeLabelItems at 31. A further 3 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 all.observe at 19 — they are counted neither in the figure above nor in this dimension's score.

Scale._computeLabelItems (cyclomatic 31) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4293
Legend._draw (cyclomatic 19) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:7782
LineController.updateElements (cyclomatic 18) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:2061
Scale._computeGridLineItems (cyclomatic 18) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4180
BarController.updateElements (cyclomatic 16) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:1387

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

What to do

  1. Bring the 19 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Scale._computeLabelItems (cyclomatic 31), chart.esm.generateTicks$1 (cyclomatic 31), Scale._computeLabelItems (cyclomatic 31). — 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 19 together lifts Cyclomatic Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity6.7 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

41 method(s) exceeded the cognitive complexity threshold of 15; the worst was Scale._computeLabelItems at 50.

Scale._computeLabelItems (cognitive 50) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4293
Scale._getYAxisLabelAlignment (cognitive 29) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4447
Legend._draw (cognitive 22) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:7782
DatasetController.parse (cognitive 21) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:731
Scale.fit (cognitive 21) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:3946

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

What to do

  1. Bring the 5 bodies over 30 down to 30 or less in Cognitive Complexity — start with Scale._computeLabelItems (cognitive 50), Scale._computeLabelItems (cognitive 50), chart.esm.generateTicks$1 (cognitive 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

26 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. Measured on part of this repository only: .js (85% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (8 lines × 2) · ×4src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommand.cs:19
Duplicated block (6 lines × 2) · ×4src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:69
Duplicated block (9 lines × 2) · ×2src/BugTracker.Persistence/Services/Data/TicketRepository.cs:226
Near-duplicate member pair (19 shared lines)src/BugTracker.Persistence/Services/Data/TicketRepository.cs:144
Duplicated block (56–65 lines × 2)src/BugTracker.Persistence/Configurations/Identity/DemoUserConfiguration.cs:17

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

What to do

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

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

D5 · Coupling8.4 / 10Strong✓ Tool-verified

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

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

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

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

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

Off the main sequence: BugTracker.Domainsrc/BugTracker.Domain/BugTracker.Domain.csproj:1

What to do

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

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

D6 · Cohesion (LCOM4)9.6 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

2 of 61 classes have LCOM4 above 3.

Low cohesion: LineController (LCOM4 4) · ×2src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:2030

What to do

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

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

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

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

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

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

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

No automated tests

What to do

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

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

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

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

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

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

No test suite found.

No tests found

What to do

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

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

D12 · Dependency Hygiene1.5 / 10Critical✓ Tool-verified

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

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

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

21 outdated, 2 vulnerable, 11 deprecated packages.

Vulnerable: AutoMapper · ×2
Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore · ×16src/BugTracker.Domain/BugTracker.Domain.csproj:8
Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore · ×12src/BugTracker.Domain/BugTracker.Domain.csproj:8
Outdated: Newtonsoft.Json · ×9

What to do

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

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

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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

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

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

1 secret(s) detected.

REDACTED

What to do

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

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

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 259 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 21 direct `PackageReference`(s), and 229 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: src/BugTracker.Persistence/Services/Data/TicketRepository.cs (28×17=476); src/BugTracker.Persistence/LogHelpers/LogHelper.cs (15×15=225) Repeated repair below the complexity floor: src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs (3 of 4 changes were fixes)

Hotspot: src/BugTracker.Persistence/Services/Data/TicketRepository.cs · ×2src/BugTracker.Persistence/Services/Data/TicketRepository.cs:513
Repeated repair: src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cssrc/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:47

What to do

  1. Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with TicketRepository.cs, LogHelper.cs. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with LogToViewHelper.cs. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

5 deducted debt markers + 8 dead symbols across 6440 LoC in the .NET projects (0.6/KLoC) → score 8.7. Measured on the .NET source only: .js (85% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

WriteOnlyPrivateField · ×3src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:17
Dead code: GetOnly · ×8src/BugTracker.Application/Contracts/Data/IAsyncRepository.cs:10
CommentedOutCodesrc/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:31
TodoCommentsrc/WebApp/BugsTracker/Areas/Tracker/Controllers/UserController.cs:61

What to do

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

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

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

The repository's root README is a clear one-page overview with an aligned demo link and a bulleted list of features plus a tech-stack table. It begins to build toward the full project structure (Quick start, installation, step-by-step flow) but is cut by the scanner before any of those sections appear in the visible text, so they cannot be flagged as missing. The README itself is well written for an overview and shows promise; it lacks a dedicated architecture or design doc, which would have been covered by the outlined :rocket: Quick start / :fire: Application presentation sections.

XML-doc coverage: BugTracker.Domain · ×5src/BugTracker.Domain/BugTracker.Domain.csproj

What to do

  1. Improve Documentation Quality — currently 7.0/10. — The repository's root README is a clear one-page overview with an aligned demo link and a bulleted list of features plus a tech-stack table. It begins to build toward the full project structure (Quick start, installation, step-by-step flow) but is cut by the scanner before any of those sections appear in the visible text, so they cannot be flagged as missing. The README itself is well written for an overview and shows promise; it lacks a dedicated architecture or design doc, which would have been covered by the outlined :rocket: Quick start / :fire: Application presentation sections.

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

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

16 valuable / 0 redundant across 21 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion6.0 / 10Adequate✓ Tool-verified

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

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

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

1 of 5 projects flagged as possibly oversized/incoherent.

Split BugTracker.Application

What to do

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

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

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

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

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

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

9 finding(s): 0 critical, 0 high, 9 medium, 0 low. semgrep hit a parse error in 2 file(s) — `src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js`, `src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED

What to do

  1. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 warning-level).
  2. 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 warning-level).

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

D30 · Dependency Vulnerabilities3.4 / 10Weak✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

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

REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

29 of 29 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/BugTracker.Persistence/Services/Data/TicketRepository.cs. Counted over 29 of the 174 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×28src/BugTracker.Persistence/Services/Identity/IdentityService.cs:1
Dormant codebase
Most significant orphaned filesrc/BugTracker.Persistence/Services/Data/TicketRepository.cs:1

What to do

  1. Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with IdentityService.cs, LogHelper.cs, TicketController.cs. — One of this dimension's main actionable groups (28 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with TicketRepository.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.8 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: TicketRepository.cs↔TicketController.cs 56%; IdentityService.cs↔UserController.cs 50%

Boundary-crossing change coupling: TicketRepository.cs ↔ TicketController.cs · ×2src/BugTracker.Persistence/Services/Data/TicketRepository.cs:1

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with TicketRepository.cs, IdentityService.cs. — One of this dimension's main actionable groups (2 issue-level).

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

D39 · IL Efficiency9.9 / 10Exemplary✓ Tool-verified

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

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

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

IL efficiency: 2 authored method(s) exceed the IL budgetsrc/BugTracker.Application/Profiles/MappingProfile.cs:31

✓ On the Gold path — maintain.

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

D44 · Platform End-of-Life6.0 / 10Adequate✓ Tool-verified

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

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

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

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

End-of-life runtime: .NET net5.0REDACTED:4

What to do

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

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

Frontend & cross-cutting dimensions

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

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

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

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

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

  • A <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) — src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:124, src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:134, src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:144

What to do

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

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

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

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

  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×8) — src/WebApp/BugsTracker/Areas/Identity/Views/Account/Login.cshtml:18, src/WebApp/BugsTracker/Areas/Identity/Views/Account/Login.cshtml:23, src/WebApp/BugsTracker/Areas/Identity/Views/Account/Register.cshtml:22, …
  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×16) — src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:48, src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:73, src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:76, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×16) — src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:9, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:166, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:182, …

What to do

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

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

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

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

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×4) — src/WebApp/BugsTracker/Areas/Identity/Views/Shared/_IdentityLayout.cshtml:3, src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/_TrackerLayout.cshtml:9, REDACTED:1, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — src/WebApp/BugsTracker/Areas/Identity/Views/Shared/_IdentityLayout.cshtml:3, src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/_TrackerLayout.cshtml:9, REDACTED:1, …
  • With more than one navigation landmark, each needs an aria-label/aria-labelledby (e.g. "Primary", "Footer") so assistive tech can tell them apart. At least one nav here is unlabelled. — src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/_TrackerLayout.cshtml:9
  • An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. (×2) — REDACTED:1, REDACTED:1
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×6) — REDACTED:101, REDACTED:112, REDACTED:137, …

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics2.1 / 10Critical✓ Tool-verified

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

  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×12) — src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:88, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:42, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:85, …
  • The repo's own CSS styles .purple-circle with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×4) — src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:139, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:140, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:141, …
  • This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_modalHolderPartial.cshtml:1

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness6.3 / 10Adequate✓ Tool-verified

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

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

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

  • aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. (×5) — src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:152, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:225, src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:331, …

What to do

  • Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety5.1 / 10Adequate✓ Tool-verified

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

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

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

  • `.wrapper .btn` sets color: #fff on background-color: #03A9F4 — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/WebApp/BugsTracker/wwwroot/css/auth.css:83
  • `.wrapper .form-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/WebApp/BugsTracker/wwwroot/css/auth.css:65
  • `button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/WebApp/BugsTracker/wwwroot/css/tracker.css:81
  • `.table-sorter-select:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/WebApp/BugsTracker/wwwroot/css/tracker.css:239
  • `.fa-spin` moves (`animation: fa-spin 2s infinite linear`) 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. (×3) — src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/all.css:105, src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/fontawesome.css:105, src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/svg-with-js.css:243
  • `.fa-pulse` moves (`animation: fa-spin 1s infinite steps(8)`) 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. (×3) — src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/all.css:109, src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/fontawesome.css:109, src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/svg-with-js.css:247
  • `.alert-success` moves (`animation: 0.5s slidein`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/WebApp/BugsTracker/wwwroot/css/tracker.css:74
  • `.modal.right.fade .modal-dialog` moves (`transition: opacity 0.3s linear, right 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/WebApp/BugsTracker/wwwroot/css/tracker.css:917

What to do

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

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

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

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

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

What to do

  • Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition5.1 / 10Adequate✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

  • The namespaces BugTracker.Domain.Entities ↔ BugTracker.Domain.Identity depend on each other. The lightest dependency in the cycle is BugTracker.Domain.Entities → BugTracker.Domain.Identity (BugTracker.Domain.Entities.ProjectTeamMember → BugTracker.Domain.Identity.ApplicationUser, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/BugTracker.Domain/Entities/ProjectTeamMember.cs:1

What to do

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

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

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

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

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

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

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

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

  • `IIdentityService` declares 25 members: `AddUserToRole`, `AuthenticateAsync`, `ConfirmEmail`, `CountManageableUsers`, `DeleteUserAsync`, `GeneratePasswordForgottenMailToken`, `GenerateRegistrationEncodedToken`, `GetAccessibleTicketTeam`, `GetAllAccessibleUsersPerRole`, `GetAllManageableUsers`, `GetCurrentTicketTeam`, `GetUserNameById`, `GetUserOrNullAsync`, `GetUserRolesById`, `ListAllRoles`, `LockOutUser`, `Register`, `RemoveUserFromRole`, `ResetPassword`, `SignOutAsync`, `UnlockUser`, `UpdateUserRoles`, `UserEmailExist`, `UserIdExists`, `UsernameExist`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/BugTracker.Application/Contracts/Identity/IIdentityService.cs:12

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX7 · Slice cohesion4.9 / 10Weak✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

  • `GetAllAccessibleMembersQueryHandler` (slice 'Team') depends on `GetAllAccessibleProjectMembersQuery` from slice 'ProjectTeam'. — src/BugTracker.Application/Features/ProjectTeam/Queries/GetAllAccessibleProjectMembers/GetAllAccessibleProjectMembersQueryHandler.cs:15
  • `ProjectWithTicketsAndTeamVm` (slice 'Projects') depends on `TicketVm` from slice 'Tickets'. — src/BugTracker.Application/Features/Projects/ProjectWithTicketsAndTeamVm.cs:14

What to do

  • Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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

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

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

C1 · Data Protection6.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

ED5 · Idempotency9.4 / 10Exemplary◐ Sampled · advisory

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

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

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

  • `Create.CreateTicketCommandHandler.Handle` mutates persistent state (a database save one hop away, in TicketRepository.AddTicketAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommandHandler.cs:32

What to do

  • Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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.

  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×4) — src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:33, src/BugTracker.Infrastructure/InfrastructureServiceRegistration.cs:21, src/BugTracker.Infrastructure/InfrastructureServiceRegistration.cs:22, …
  • A placeholder value ("John doe") is still in shipped code — sample/mock data that was never replaced with the real thing. — src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:29
  • A placeholder value ("JOHN DOE") is still in shipped code — sample/mock data that was never replaced with the real thing. — src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:30
  • A placeholder value ("Jane doe") is still in shipped code — sample/mock data that was never replaced with the real thing. — src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:42
  • A placeholder value ("JANE DOE") is still in shipped code — sample/mock data that was never replaced with the real thing. — src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:43

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

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

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

What to do

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

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

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

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Adopt pino (or winston) and log at meaningful points in the services you run.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

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

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

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

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

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

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/WebApp/BugsTracker/Program.cs:22

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

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

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

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

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

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

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 39/158 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/BugTracker.Persistence/LogHelpers/LogHelper.cs:23, src/BugTracker.Persistence/LogHelpers/LogHelper.cs:36, src/BugTracker.Persistence/LogHelpers/LogHelper.cs:53, …

What to do

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

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

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

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

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

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

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

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

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

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

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

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This method contradicts itself about `model`: line 15 assigns it with `as BaseResponse`, which hands back null rather than throwing when the value is not a `BaseResponse`, but line 16 then dereferences it directly as `model.StatusCode` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `model` once before the first use and handle the null case, or cast with `(BaseResponse)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WebApp/BugsTracker/Filters/Validation/ValidationFilter.cs:16
  • 0/5 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.

What to do

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

WCAG coverage — what static analysis assessed

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

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

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

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health65%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture73%StrongSolid.
Maturity40%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness12%Critical — gated by D8, D9, D12, P1, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security74%Adequate — gated by D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility30%Weak — gated by AC1, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for

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

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

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX2 Stateful singletons — no singleton implementations detected
  • AX8 Test isolation — no test/production split to check
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the service exited before it opened a port — `ASPNETCORE_URLS=http://127.0.0.1:0 ASPNETCORE_ENVIRONMENT=Development dotnet run --no-build --no-launch-profile --project 'REDACTED'`: share/dotnet The following frameworks were found: 6.0.36 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 7.0.20 at [/usr/share/dotnet/shared/Microsoft.AspNetCore.App] 8.0.27 at [/usr/sha…; runtime evidence skipped (launch chosen because REDACTED is a Microsoft.NET.Sdk.Web project) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D16 Bus Factor — bus factor 1 — one contributor carries this repository
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D3 God Classes — Most of this repository's production source (.js) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a message-bus package; 29 CQRS handler(s)
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 72 finding(s)
AC2 · Forms & labels · Link with no accessible name · ×16
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:48 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:73 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:76 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:98 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:101 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:51 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:67 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:121 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_basePagerBarPartial.cshtml:7 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_basePagerBarPartial.cshtml:10 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_basePagerBarPartial.cshtml:32 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_basePagerBarPartial.cshtml:35 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_pagerBarPartial.cshtml:9 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_pagerBarPartial.cshtml:12 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_pagerBarPartial.cshtml:37 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_pagerBarPartial.cshtml:40 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels · <input> without a programmatic label · ×15
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Identity/Views/Account/Login.cshtml:18 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Identity/Views/Account/Login.cshtml:23 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Identity/Views/Account/Register.cshtml:22 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Identity/Views/Account/Register.cshtml:27 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Identity/Views/Account/Register.cshtml:32 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Identity/Views/Account/Register.cshtml:39 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Identity/Views/Account/Register.cshtml:44 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:16 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:166 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_createProjectModalPartial.cshtml:31 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_createProjectModalPartial.cshtml:137 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_deleteProjectModalPartial.cshtml:19 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_deleteProjectModalPartial.cshtml:35 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_updateProjectModalPartial.cshtml:33 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_updateProjectModalPartial.cshtml:141 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · <select> without a programmatic label · ×5
  • <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:9 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:182 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:191 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:199 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:207 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC5 · ARIA correctness · aria-hidden hides a focusable element · ×5
  • aria-hidden hides a focusable element src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:152 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
  • aria-hidden hides a focusable element src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:225 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
  • aria-hidden hides a focusable element src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:331 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
  • aria-hidden hides a focusable element src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:426 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
  • aria-hidden hides a focusable element src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml:131 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
AC2 · Forms & labels · <textarea> without a programmatic label · ×4
  • <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_createProjectModalPartial.cshtml:36 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_createProjectModalPartial.cshtml:142 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_updateProjectModalPartial.cshtml:38 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Project/_updateProjectModalPartial.cshtml:146 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · <html> without a lang · ×4
  • <html> without a lang src/WebApp/BugsTracker/Areas/Identity/Views/Shared/_IdentityLayout.cshtml:3 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/_TrackerLayout.cshtml:9 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang REDACTED:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang REDACTED:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×4
  • Clickable element isn't keyboard-operable src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:139 — The repo's own CSS styles .purple-circle with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:140 — The repo's own CSS styles .purple-circle with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:141 — The repo's own CSS styles .purple-circle with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:142 — The repo's own CSS styles .purple-circle with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
D30 · Dependency Vulnerabilities · High CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×3
  • WriteOnlyPrivateField src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:17 — private ITicketConfigurationRepository _ticketConfigurationRepository — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/BugTracker.Application/Features/Tickets/Queries/GetTicketsByUser/GetTicketByUserQueryHandler.cs:20 — private ITicketConfigurationRepository _ticketConfigurationRepository — 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 REDACTED:11 — private ILogger<HomeController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Document <title> is empty · ×2
  • Document <title> is empty REDACTED:1 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
  • Document <title> is empty REDACTED:1 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
D12 · Dependency Hygiene · Vulnerable · ×2
  • Vulnerable: AutoMapper — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: Azure.Identity — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: TicketRepository.cs ↔ TicketController.cs src/BugTracker.Persistence/Services/Data/TicketRepository.cs:1 — `src/BugTracker.Persistence/Services/Data/TicketRepository.cs` (context BugTracker) and `src/WebApp/BugsTracker/Areas/Tracker/Controllers/TicketController.cs` (context WebApp) sit in DIFFERENT parts of the tree yet change together 56% of the time (14 of the 25 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `58ae07c6` Fixed project tickets pagination.; `28232afc` Rework the way admin retrieve the tickets overview.; `c59e6d79` SearchString and pagination fixed for dev on Tickets page. — run `git show` on any of them.
  • Boundary-crossing change coupling: IdentityService.cs ↔ UserController.cs src/BugTracker.Persistence/Services/Identity/IdentityService.cs:1 — `src/BugTracker.Persistence/Services/Identity/IdentityService.cs` (context BugTracker) and `src/WebApp/BugsTracker/Areas/Tracker/Controllers/UserController.cs` (context WebApp) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `ac05ed35` Admin can filter pending users on user management page.; `599c23e8` Deleting user functional. Improve logging system to keep tracks of de…; `3563abc2` Added pagination to users result. — run `git show` on any of them.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/BugTracker.Domain/Entities/ProjectTeamMember.cs:1 — The namespaces BugTracker.Domain.Entities ↔ BugTracker.Domain.Identity depend on each other. The lightest dependency in the cycle is BugTracker.Domain.Entities → BugTracker.Domain.Identity (BugTracker.Domain.Entities.ProjectTeamMember → BugTracker.Domain.Identity.ApplicationUser, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Serious — 218 finding(s)
X2 · Cancellation propagation · Async method without CancellationToken · ×39
  • Async method without CancellationToken: OnBeforeSaveChangesAsync src/BugTracker.Persistence/LogHelpers/LogHelper.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: MapEntries src/BugTracker.Persistence/LogHelpers/LogHelper.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: MapPropertiesToEntryValue src/BugTracker.Persistence/LogHelpers/LogHelper.cs:53 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: MapFKToAuditEntryValue src/BugTracker.Persistence/LogHelpers/LogHelper.cs:75 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AssignValuesBasedOnEntryState src/BugTracker.Persistence/LogHelpers/LogHelper.cs:114 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAudits src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ListAll src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CountAll src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:93 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs:27 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeleteAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetByIdAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs:40 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetOnly src/BugTracker.Persistence/Services/Data/BaseRepository.cs:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ListAllAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ListAllAsync src/BugTracker.Persistence/Services/Data/BaseRepository.cs:55 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetByTicket src/BugTracker.Persistence/Services/Data/CommentRepository.cs:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AddProjectAsync src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:24 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateProjectAsync src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:36 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ListAll src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:58 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CountProject src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetProjectIdByTicketId src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:102 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UserBelongsToProjectTeam src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:107 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetProjectTeamIds src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:111 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: NameIsUnique src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:115 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateProjectTeam_ProjectManager src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:126 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
D12 · Dependency Hygiene · Deprecated · ×16
  • Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore src/BugTracker.Domain/BugTracker.Domain.csproj:8 — Microsoft.AspNetCore.Identity.EntityFrameworkCore 5.0.11 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED:9 — Microsoft.AspNetCore.Identity.EntityFrameworkCore 5.0.11 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED:17 — Microsoft.AspNetCore.Identity.EntityFrameworkCore 5.0.11 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore REDACTED:8 — Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore 5.0.11 — Other,Legacy
  • Deprecated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:10 — Microsoft.EntityFrameworkCore.SqlServer 5.0.11 — Other,Legacy
  • Deprecated: Microsoft.EntityFrameworkCore.Tools REDACTED:11 — Microsoft.EntityFrameworkCore.Tools 5.0.11 — Other,Legacy
  • Deprecated: Microsoft.EntityFrameworkCore.Tools REDACTED:20 — Microsoft.EntityFrameworkCore.Tools 5.0.11 — Other,Legacy
  • Deprecated: microsoft.extensions.dependencyinjection REDACTED:15 — microsoft.extensions.dependencyinjection 5.0.2 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:17 — Microsoft.Extensions.Options.ConfigurationExtensions 5.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:9 — Microsoft.Extensions.Options.ConfigurationExtensions 5.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:19 — Microsoft.Extensions.Options.ConfigurationExtensions 5.0.0 — Other,Legacy
  • Deprecated: Microsoft.Extensions.Configuration.Abstractions REDACTED:8 — Microsoft.Extensions.Configuration.Abstractions 5.0.0 — Other,Legacy
  • Deprecated: FluentValidation.AspNetCore REDACTED:11 — FluentValidation.AspNetCore 10.3.4 — Legacy
  • Deprecated: Azure.Identity REDACTED:12 — REDACTED — Other
  • Deprecated: Microsoft.AspNetCore.Mvc.Core REDACTED:14 — Microsoft.AspNetCore.Mvc.Core 2.2.5 — Other,Legacy
  • Deprecated: Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation REDACTED:15 — Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation 5.0.11 — Other,Legacy
AC4 · Keyboard semantics · Anchor without href · ×12
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:88 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:42 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:85 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:103 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:230 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:362 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Project/Details.cshtml:368 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_basePagerBarPartial.cshtml:22 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_pagerBarPartial.cshtml:26 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ByUser.cshtml:90 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/Ticket/ProjectTickets.cshtml:57 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/WebApp/BugsTracker/Areas/Tracker/Views/User/GetAll.cshtml:100 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×8
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/all.css:105 — `.fa-spin` moves (`animation: fa-spin 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/all.css:109 — `.fa-pulse` moves (`animation: fa-spin 1s infinite steps(8)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/fontawesome.css:105 — `.fa-spin` moves (`animation: fa-spin 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/fontawesome.css:109 — `.fa-pulse` moves (`animation: fa-spin 1s infinite steps(8)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/svg-with-js.css:243 — `.fa-spin` moves (`animation: fa-spin 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/lib/font-awesome/css/svg-with-js.css:247 — `.fa-pulse` moves (`animation: fa-spin 1s infinite steps(8)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/css/tracker.css:74 — `.alert-success` moves (`animation: 0.5s slidein`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/WebApp/BugsTracker/wwwroot/css/tracker.css:917 — `.modal.right.fade .modal-dialog` moves (`transition: opacity 0.3s linear, right 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D17 · Explicit Debt · Dead code · ×8
  • Dead code: GetOnly src/BugTracker.Application/Contracts/Data/IAsyncRepository.cs:10 — Method GetOnly — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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: UpdateAsync src/BugTracker.Application/Contracts/Data/IAsyncRepository.cs:16 — Method UpdateAsync — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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: GetTypeName src/BugTracker.Application/Contracts/Data/ITicketConfigurationRepository.cs:12 — Method GetTypeName — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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: GetPriorityName src/BugTracker.Application/Contracts/Data/ITicketConfigurationRepository.cs:14 — Method GetPriorityName — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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: GetStatusName src/BugTracker.Application/Contracts/Data/ITicketConfigurationRepository.cs:16 — Method GetStatusName — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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: AddUserToRole src/BugTracker.Application/Contracts/Identity/IIdentityService.cs:14 — Method AddUserToRole — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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: RemoveUserFromRole src/BugTracker.Application/Contracts/Identity/IIdentityService.cs:31 — Method RemoveUserFromRole — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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: UsernameExist src/BugTracker.Application/Contracts/Identity/IIdentityService.cs:38 — Method UsernameExist — Roslyn's SymbolFinder walked every project the solution loads, including BugTracker.Application, 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.
AC3 · Page structure · Data table has no header cells · ×6
  • Data table has no header cells REDACTED:101 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells REDACTED:112 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells REDACTED:137 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells REDACTED:101 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells REDACTED:112 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells REDACTED:137 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Page without a main landmark · ×4
  • Page without a main landmark src/WebApp/BugsTracker/Areas/Identity/Views/Shared/_IdentityLayout.cshtml:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/_TrackerLayout.cshtml:9 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark REDACTED:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark REDACTED:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×4
  • Duplicated block (8 lines × 2) src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommand.cs:19 — src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommand.cs:19-26 | src/BugTracker.Application/Features/Tickets/Commands/Update/UpdateTicketCommand.cs:19-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:70 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:70-78 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:99-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:70` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:175 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:175-182 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:199-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:175` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:173` calls `Where`, `Parse` and `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:197` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:549 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:549-556 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:563-571 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:549` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:546` calls `Where`, `Contains` and `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:560` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×4
  • Duplicated block (6 lines × 2) src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:69 — src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:69-74 | src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:123-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:159 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:159-164 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:252-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:169 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:169-174 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:260-265 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:169` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (6 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:542 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:542-547 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:593-598 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:542` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
AC1 · Text alternatives · <canvas> without a text alternative · ×3
  • <canvas> without a text alternative src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:124 — 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 src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:134 — 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 src/WebApp/BugsTracker/Areas/Tracker/Views/Home/Dashboard.cshtml:144 — 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.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×3
  • Focus outline removed in CSS without a :focus replacement src/WebApp/BugsTracker/wwwroot/css/auth.css:65 — `.wrapper .form-field input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/WebApp/BugsTracker/wwwroot/css/tracker.css:81 — `button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/WebApp/BugsTracker/wwwroot/css/tracker.css:239 — `.table-sorter-select:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AX7 · Slice cohesion · Cross-slice coupling · ×2
  • Cross-slice coupling: Team → ProjectTeam src/BugTracker.Application/Features/ProjectTeam/Queries/GetAllAccessibleProjectMembers/GetAllAccessibleProjectMembersQueryHandler.cs:15 — `GetAllAccessibleMembersQueryHandler` (slice 'Team') depends on `GetAllAccessibleProjectMembersQuery` from slice 'ProjectTeam'.
  • Cross-slice coupling: Projects → Tickets src/BugTracker.Application/Features/Projects/ProjectWithTicketsAndTeamVm.cs:14 — `ProjectWithTicketsAndTeamVm` (slice 'Projects') depends on `TicketVm` from slice 'Tickets'.
D1 · Cyclomatic Complexity · Scale._computeLabelItems (cyclomatic 31) · ×2
  • Scale._computeLabelItems (cyclomatic 31) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4293 — Scale._computeLabelItems has cyclomatic complexity 31 (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.
  • Scale._computeLabelItems (cyclomatic 31) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:5558 — Scale._computeLabelItems has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Legend._draw (cyclomatic 19) · ×2
  • Legend._draw (cyclomatic 19) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:7782 — Legend._draw has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 7867, drawLegendBox). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • Legend._draw (cyclomatic 19) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:10408 — Legend._draw has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 10493, drawLegendBox). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · LineController.updateElements (cyclomatic 18) · ×2
  • LineController.updateElements (cyclomatic 18) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:2061 — LineController.updateElements has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • LineController.updateElements (cyclomatic 18) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:8373 — LineController.updateElements has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Scale._computeGridLineItems (cyclomatic 18) · ×2
  • Scale._computeGridLineItems (cyclomatic 18) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4180 — Scale._computeGridLineItems has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • Scale._computeGridLineItems (cyclomatic 18) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:5445 — Scale._computeGridLineItems has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · BarController.updateElements (cyclomatic 16) · ×2
  • BarController.updateElements (cyclomatic 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:1387 — BarController.updateElements has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • BarController.updateElements (cyclomatic 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:7699 — BarController.updateElements has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D15 · Churn × Complexity Hotspots · Hotspot · ×2
  • Hotspot: src/BugTracker.Persistence/Services/Data/TicketRepository.cs src/BugTracker.Persistence/Services/Data/TicketRepository.cs:513 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in TicketRepository.LookoutTicketBySearchString at line 513. 7 of those changes were fix/bug commits, and the other 21 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 2022-01-15..2022-04-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2022-01-15 10:49:34 +02:00' --until='2022-04-15 10:49:34 +02:00' --full-history --no-merges -- src/BugTracker.Persistence/Services/Data/TicketRepository.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: src/BugTracker.Persistence/LogHelpers/LogHelper.cs src/BugTracker.Persistence/LogHelpers/LogHelper.cs:114 — src/BugTracker.Persistence/LogHelpers/LogHelper.cs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in LogHelper.AssignValuesBasedOnEntryState at line 114. 4 of those changes were fix/bug commits, and the other 11 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 2022-01-15..2022-04-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2022-01-15 10:49:34 +02:00' --until='2022-04-15 10:49:34 +02:00' --full-history --no-merges -- src/BugTracker.Persistence/LogHelpers/LogHelper.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.
D2 · Cognitive Complexity · Scale._computeLabelItems (cognitive 50) · ×2
  • Scale._computeLabelItems (cognitive 50) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4293 — Scale._computeLabelItems has cognitive complexity 50 (threshold 15). Drivers by points: if/else 25 (40 pts), match/switch 2 (6 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Scale._computeLabelItems (cognitive 50) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:5558 — Scale._computeLabelItems has cognitive complexity 50 (threshold 15). Drivers by points: if/else 25 (40 pts), match/switch 2 (6 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Scale._getYAxisLabelAlignment (cognitive 29) · ×2
  • Scale._getYAxisLabelAlignment (cognitive 29) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4447 — Scale._getYAxisLabelAlignment has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (29 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Scale._getYAxisLabelAlignment (cognitive 29) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:5712 — Scale._getYAxisLabelAlignment has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (29 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Legend._draw (cognitive 22) · ×2
  • Legend._draw (cognitive 22) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:7782 — Legend._draw has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 6 (nesting depth added 3). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 7867, drawLegendBox). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • Legend._draw (cognitive 22) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:10408 — Legend._draw has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 6 (nesting depth added 3). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 10493, drawLegendBox). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · DatasetController.parse (cognitive 21) · ×2
  • DatasetController.parse (cognitive 21) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:731 — DatasetController.parse has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (nesting depth added 7). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • DatasetController.parse (cognitive 21) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:4151 — DatasetController.parse has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (nesting depth added 7). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Scale.fit (cognitive 21) · ×2
  • Scale.fit (cognitive 21) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:3946 — Scale.fit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (8 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Scale.fit (cognitive 21) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:5211 — Scale.fit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (8 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Scale._computeGridLineItems (cognitive 21) · ×2
  • Scale._computeGridLineItems (cognitive 21) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4180 — Scale._computeGridLineItems has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • Scale._computeGridLineItems (cognitive 21) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:5445 — Scale._computeGridLineItems has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · BarController.updateElements (cognitive 19) · ×2
  • BarController.updateElements (cognitive 19) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:1387 — BarController.updateElements has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 6, if/else 1 (2 pts), loops 1 (nesting depth added 6). 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.
  • BarController.updateElements (cognitive 19) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:7699 — BarController.updateElements has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 6, if/else 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Animations._createAnimations (cognitive 16) · ×2
  • Animations._createAnimations (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:350 — Animations._createAnimations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1 (nesting depth added 6). 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.
  • Animations._createAnimations (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:3770 — Animations._createAnimations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BarController._getStacks (cognitive 16) · ×2
  • BarController._getStacks (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:1420 — BarController._getStacks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1 (nesting depth added 6). 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.
  • BarController._getStacks (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:7732 — BarController._getStacks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LineController.updateElements (cognitive 16) · ×2
  • LineController.updateElements (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:2061 — LineController.updateElements has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 3 (6 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • LineController.updateElements (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:8373 — LineController.updateElements has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 3 (6 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Scale._computeLabelSizes (cognitive 16) · ×2
  • Scale._computeLabelSizes (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:4072 — Scale._computeLabelSizes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 6). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Scale._computeLabelSizes (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:5337 — Scale._computeLabelSizes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 6). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:226 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:226-234 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:268-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:226` 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 (9 lines × 2) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:242 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:242-250 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:285-293 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:242` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: LineController (LCOM4 4) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:2030 — LineController's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: LineController (LCOM4 4) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:8342 — LineController's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC3 · Page structure · Multiple navigation landmarks without distinguishing labels · ×1
  • Multiple navigation landmarks without distinguishing labels src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/_TrackerLayout.cshtml:9 — With more than one navigation landmark, each needs an aria-label/aria-labelledby (e.g. "Primary", "Footer") so assistive tech can tell them apart. At least one nav here is unlabelled.
AC4 · Keyboard semantics · Modal dialog does not manage focus · ×1
  • Modal dialog does not manage focus src/WebApp/BugsTracker/Areas/Tracker/Views/Shared/Partial/Common/_modalHolderPartial.cshtml:1 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.6 · ×1
  • Low contrast colour pair in CSS (2.6:1) src/WebApp/BugsTracker/wwwroot/css/auth.css:83 — `.wrapper .btn` sets color: #fff on background-color: #03A9F4 — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 34 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · chart.esm.generateTicks$1 (cyclomatic 31) · ×1
  • chart.esm.generateTicks$1 (cyclomatic 31) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:9323 — chart.esm.generateTicks$1 has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · chart.generateTicks$1 (cyclomatic 31) · ×1
  • chart.generateTicks$1 (cyclomatic 31) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:11949 — chart.generateTicks$1 has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · chart.drawPoint (cyclomatic 19) · ×1
  • chart.drawPoint (cyclomatic 19) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:1246 — chart.drawPoint has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · all.icon (cyclomatic 17) · ×1
  • all.icon (cyclomatic 17) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js:4267 — all.icon has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: all.observe (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · fontawesome.icon (cyclomatic 17) · ×1
  • fontawesome.icon (cyclomatic 17) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js:2284 — fontawesome.icon has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: fontawesome.observe (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · TicketRepository.GetTicketsByUser (cyclomatic 16) · ×1
  • TicketRepository.GetTicketsByUser (cyclomatic 16) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:218 — TicketRepository.GetTicketsByUser has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 240, 283). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This is NOT this file's highest cyclomatic complexity: TicketRepository.LookoutTicketBySearchString (cyclomatic 17) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · chart._longestText (cyclomatic 16) · ×1
  • chart._longestText (cyclomatic 16) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:1197 — chart._longestText has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · all.makeInlineSvgAbstract (cyclomatic 16) · ×1
  • all.makeInlineSvgAbstract (cyclomatic 16) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js:2918 — all.makeInlineSvgAbstract has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: all.observe (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · fontawesome.makeInlineSvgAbstract (cyclomatic 16) · ×1
  • fontawesome.makeInlineSvgAbstract (cyclomatic 16) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js:935 — fontawesome.makeInlineSvgAbstract has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: fontawesome.observe (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:47 — src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.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 7 (its worst body is LogToViewHelper.ManageTeam at line 47), 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: “Fixed log display bug preventing to access data.”; “Minor fix in log to view helper.”; “Fixed bug retrieving user role.”. 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 2022-01-15..2022-04-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2022-01-15 10:49:34 +02:00' --until='2022-04-15 10:49:34 +02:00' --full-history --no-merges -- src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.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.
D16 · Bus Factor · bus factor 1 · ×1
  • bus factor 1 — one contributor carries this repository — 2 contributor(s) have commits in this repository (automation and bot accounts excluded), but the commits of a single one of them cover most of its history — 81% of the 264 commit(s) sampled — so the number of people who actually carry it is 1. This is not the ambient state of a solo project: there ARE other contributors, and if the one who carries the repository becomes unavailable, the knowledge behind most of its history goes with them. Spread the next changes deliberately — have a second contributor review or pair on them — and write down the parts only one person can currently change.
D17 · Explicit Debt · CommentedOutCode · ×1
  • CommentedOutCode src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:31 — 4 consecutive commented-code lines
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment src/WebApp/BugsTracker/Areas/Tracker/Controllers/UserController.cs:61 — //TODO manage errors — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · chart.esm.generateTicks$1 (cognitive 34) · ×1
  • chart.esm.generateTicks$1 (cognitive 34) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:9323 — chart.esm.generateTicks$1 has cognitive complexity 34 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 7, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · chart.generateTicks$1 (cognitive 34) · ×1
  • chart.generateTicks$1 (cognitive 34) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:11949 — chart.generateTicks$1 has cognitive complexity 34 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 7, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LogHelper.AssignValuesBasedOnEntryState (cognitive 31) · ×1
  • LogHelper.AssignValuesBasedOnEntryState (cognitive 31) src/BugTracker.Persistence/LogHelpers/LogHelper.cs:114 — LogHelper.AssignValuesBasedOnEntryState has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · chart.esm.minMaxDecimation (cognitive 26) · ×1
  • chart.esm.minMaxDecimation (cognitive 26) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:6963 — chart.esm.minMaxDecimation has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 4, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · chart.minMaxDecimation (cognitive 26) · ×1
  • chart.minMaxDecimation (cognitive 26) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:9589 — chart.minMaxDecimation has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 4, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · chart.esm.placeBoxes (cognitive 22) · ×1
  • chart.esm.placeBoxes (cognitive 22) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.esm.js:2873 — chart.esm.placeBoxes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · chart.placeBoxes (cognitive 22) · ×1
  • chart.placeBoxes (cognitive 22) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:2193 — chart.placeBoxes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · all.replaceForPosition (cognitive 22) · ×1
  • all.replaceForPosition (cognitive 22) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js:3977 — all.replaceForPosition has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 7). None of this is in the body itself: all 22 points belong to 2 function literals inside it that branch (lines 3979, 4020). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · fontawesome.replaceForPosition (cognitive 22) · ×1
  • fontawesome.replaceForPosition (cognitive 22) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js:1994 — fontawesome.replaceForPosition has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 7). None of this is in the body itself: all 22 points belong to 2 function literals inside it that branch (lines 1996, 2037). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · chart._longestText (cognitive 20) · ×1
  • chart._longestText (cognitive 20) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:1197 — chart._longestText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · all.handleThenable (cognitive 20) · ×1
  • all.handleThenable (cognitive 20) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js:2370 — all.handleThenable has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 2, error handling 1 (nesting depth added 9). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2383, 2393). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · fontawesome.handleThenable (cognitive 20) · ×1
  • fontawesome.handleThenable (cognitive 20) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js:387 — fontawesome.handleThenable has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 2, error handling 1 (nesting depth added 9). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 400, 410). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · all.icon (cognitive 18) · ×1
  • all.icon (cognitive 18) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js:4267 — all.icon has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11, if/else 4 (5 pts), boolean chains 2 (nesting depth added 1). Of this number, 12 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · fontawesome.icon (cognitive 18) · ×1
  • fontawesome.icon (cognitive 18) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js:2284 — fontawesome.icon has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11, if/else 4 (5 pts), boolean chains 2 (nesting depth added 1). Of this number, 12 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · chart._boundSegment (cognitive 17) · ×1
  • chart._boundSegment (cognitive 17) src/WebApp/BugsTracker/wwwroot/lib/Chart.js/chart.js:2964 — chart._boundSegment has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 1 (nesting depth added 4). Of this number, 13 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · all.makeInlineSvgAbstract (cognitive 16) · ×1
  • all.makeInlineSvgAbstract (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js:2918 — all.makeInlineSvgAbstract has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, ternaries 6, if/else 4. Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · all.onTree (cognitive 16) · ×1
  • all.onTree (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/all.js:3898 — all.onTree has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 2, ternaries 2, boolean chains 1 (nesting depth added 3). Of this number, 8 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · fontawesome.makeInlineSvgAbstract (cognitive 16) · ×1
  • fontawesome.makeInlineSvgAbstract (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js:935 — fontawesome.makeInlineSvgAbstract has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, ternaries 6, if/else 4. Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · fontawesome.onTree (cognitive 16) · ×1
  • fontawesome.onTree (cognitive 16) src/WebApp/BugsTracker/wwwroot/lib/font-awesome/js/fontawesome.js:1915 — fontawesome.onTree has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 2, ternaries 2, boolean chains 1 (nesting depth added 3). Of this number, 8 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D4 · Code Duplication · Near-duplicate member pair (19 shared lines) · ×1
  • Near-duplicate member pair (19 shared lines) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:144 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:144-182 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:219-318 — These two members are variants of one another: 19 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Duplicated block (56–65 lines × 2) · ×1
  • Duplicated block (56–65 lines × 2) src/BugTracker.Persistence/Configurations/Identity/DemoUserConfiguration.cs:17 — src/BugTracker.Persistence/Configurations/Identity/DemoUserConfiguration.cs:17-72 | src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:52-116 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:117` calls `HasData` and `src/BugTracker.Persistence/Configurations/Identity/DemoUserConfiguration.cs:73` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommandValidator.cs:18 — src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommandValidator.cs:18-47 | src/BugTracker.Application/Features/Tickets/Commands/Update/UpdateTicketCommandValidator.cs:18-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) src/BugTracker.Persistence/Configurations/Identity/UserRolesConfiguration.cs:67 — src/BugTracker.Persistence/Configurations/Identity/UserRolesConfiguration.cs:67-92 | src/BugTracker.Persistence/Configurations/Identity/UserRolesConfiguration.cs:95-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Persistence/Configurations/Identity/UserRolesConfiguration.cs:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:130 — src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:130-148 | src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:160-178 — 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/BugTracker.Application/Features/Tickets/Commands/Delete/DeleteTicketCommandHandler.cs:44 — src/BugTracker.Application/Features/Tickets/Commands/Delete/DeleteTicketCommandHandler.cs:44-60 | src/BugTracker.Application/Features/Tickets/Commands/Update/UpdateTicketCommandHandler.cs:60-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) src/BugTracker.Application/Features/Comments/Commands/Create/CreateCommentCommandHandler.cs:53 — src/BugTracker.Application/Features/Comments/Commands/Create/CreateCommentCommandHandler.cs:53-69 | src/BugTracker.Application/Features/Tickets/Commands/Delete/DeleteTicketCommandHandler.cs:44-60 | src/BugTracker.Application/Features/Tickets/Commands/Update/UpdateTicketCommandHandler.cs:60-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/BugTracker.Application/Features/Projects/Commands/Create/CreateProjectCommandValidator.cs:18 — src/BugTracker.Application/Features/Projects/Commands/Create/CreateProjectCommandValidator.cs:18-33 | src/BugTracker.Application/Features/Projects/Commands/Update/UpdateProjectCommandValidator.cs:17-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×1
  • Duplicated block (14–15 lines × 3) src/BugTracker.Application/Features/ProjectTeam/Queries/GetAllAccessibleProjectMembers/GetAllAccessibleProjectMembersQueryHandler.cs:33 — src/BugTracker.Application/Features/ProjectTeam/Queries/GetAllAccessibleProjectMembers/GetAllAccessibleProjectMembersQueryHandler.cs:33-47 | src/BugTracker.Application/Features/TicketTeam/Query/GetAccessibleTeam/GetAllAccessibleTicketMembersQueryHandler.cs:30-43 | src/BugTracker.Application/Features/TicketTeam/Query/GetCurrentTeam/GetCurrentTeamQueryHandler.cs:29-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/BugTracker.Application/Features/ProjectTeam/Queries/GetAllAccessibleProjectMembers/GetAllAccessibleProjectMembersQueryHandler.cs:33` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GetAllAccessibleTicketMembersQuery` in one and `GetCurrentTeamQuery` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) src/BugTracker.Application/Features/Projects/Commands/Create/CreateProjectCommandValidator.cs:19 — src/BugTracker.Application/Features/Projects/Commands/Create/CreateProjectCommandValidator.cs:19-28 | src/BugTracker.Application/Features/Projects/Commands/Update/UpdateProjectCommandValidator.cs:18-27 | src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommandValidator.cs:19-28 | src/BugTracker.Application/Features/Tickets/Commands/Update/UpdateTicketCommandValidator.cs:19-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (9–11 lines × 3) · ×1
  • Duplicated block (9–11 lines × 3) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:29 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:29-39 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:119-129 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:149-157 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–10 lines × 6) · ×1
  • Duplicated block (7–10 lines × 6) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:30 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:30-39 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:120-129 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:151-157 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:189-195 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:230-236 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:272-278 — all 6 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:27` calls `Where`, `Select`, `ToListAsync` and `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:227` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:58 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:58-65 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:86-93 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:374-381 — 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 `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:393 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:393-399 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:554-560 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:600-606 — 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 `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:393` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:400` calls `Where`, `Intersect`, `Contains` and `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:607` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:60 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:60-65 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:88-93 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:376-381 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:515-520 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) src/BugTracker.Application/Features/Tickets/Queries/GetProjectTickets/GetProjectTicketsQueryHandler.cs:84 — src/BugTracker.Application/Features/Tickets/Queries/GetProjectTickets/GetProjectTicketsQueryHandler.cs:84-88 | src/BugTracker.Application/Features/Tickets/Queries/GetTicketsByUser/GetTicketByUserQueryHandler.cs:58-62 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `response` to `ApiResponse<ProjectWithTicketVm>` in one and `ApiResponse<UserTicketsVm>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) src/BugTracker.Persistence/Services/Data/TicketRepository.cs:45 — src/BugTracker.Persistence/Services/Data/TicketRepository.cs:45-50 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:175-180 | src/BugTracker.Persistence/Services/Data/TicketRepository.cs:199-204 — 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 `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:45` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:173` calls `Where`, `Parse` and `src/BugTracker.Persistence/Services/Data/TicketRepository.cs:197` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET net5.0 REDACTED:4 — REDACTED declares .NET net5.0 as this project's target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: BugTracker.Domain src/BugTracker.Domain/BugTracker.Domain.csproj:1 — BugTracker.Domain: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
ED5 · Idempotency · Non-idempotent mutation · ×1
  • Non-idempotent mutation: Create.CreateTicketCommandHandler.Handle src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommandHandler.cs:32 — `Create.CreateTicketCommandHandler.Handle` mutates persistent state (a database save one hop away, in TicketRepository.AddTicketAsync) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 13 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×1
  • Symbol treated as nullable, then dereferenced unguarded src/WebApp/BugsTracker/Filters/Validation/ValidationFilter.cs:16 — This method contradicts itself about `model`: line 15 assigns it with `as BaseResponse`, which hands back null rather than throwing when the value is not a `BaseResponse`, but line 16 then dereferences it directly as `model.StatusCode` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `model` once before the first use and handle the null case, or cast with `(BaseResponse)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Minor — 64 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×28
  • Orphaned file src/BugTracker.Persistence/Services/Identity/IdentityService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/LogHelpers/LogHelper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/WebApp/BugsTracker/Areas/Tracker/Controllers/TicketController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/Services/Data/ProjectRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/Services/Audits/AuditRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/WebApp/BugsTracker/Areas/Tracker/Controllers/UserController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/IdentityServiceExtension.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Tickets/Queries/GetProjectTickets/GetProjectTicketsQueryHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/Configurations/Identity/UserRolesConfiguration.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Tickets/Queries/GetTicketsByUser/GetTicketByUserQueryHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/WebApp/BugsTracker/Areas/Tracker/Controllers/ProjectController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Tickets/Queries/GetTicketDiagramDataByUser/GetTicketDiagramDataByUserQueryHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Profiles/MappingProfile.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/WebApp/BugsTracker/Startup.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Tickets/Commands/Update/UpdateTicketCommandHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/Configurations/Identity/DemoUserConfiguration.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Infrastructure/Mail/EmailService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Comments/Commands/Create/CreateCommentCommandHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Persistence/ApplicationDbContext.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Audits/Queries/GetAllLogs/GetAllLogsQueryHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/Tickets/Commands/Create/CreateTicketCommandHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/BugTracker.Application/Features/UserManagement/Queries/GetAllUsers/GetAllUsersQueryHandler.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 3 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×12
  • Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore src/BugTracker.Domain/BugTracker.Domain.csproj:8 — Microsoft.AspNetCore.Identity.EntityFrameworkCore 5.0.11 → 10.0.13 available (referenced by BugTracker.Domain).
  • Outdated: Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore REDACTED:8 — Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore 5.0.11 → 10.0.13 available (referenced by BugTracker.Persistence).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer REDACTED:10 — Microsoft.EntityFrameworkCore.SqlServer 5.0.11 → 10.0.13 available (referenced by BugTracker.Persistence).
  • Outdated: Microsoft.EntityFrameworkCore.Tools REDACTED:11 — Microsoft.EntityFrameworkCore.Tools 5.0.11 → 10.0.13 available (referenced by BugTracker.Persistence).
  • Outdated: microsoft.extensions.dependencyinjection REDACTED:15 — microsoft.extensions.dependencyinjection 5.0.2 → 10.0.13 available (referenced by BugTracker.Persistence).
  • Outdated: Microsoft.Extensions.Options.ConfigurationExtensions REDACTED:9 — Microsoft.Extensions.Options.ConfigurationExtensions 5.0.0 → 10.0.13 available (referenced by BugTracker.Persistence).
  • Outdated: Microsoft.Extensions.Configuration.Abstractions REDACTED:8 — Microsoft.Extensions.Configuration.Abstractions 5.0.0 → 10.0.13 available (referenced by BugTracker.Infrastructure).
  • Outdated: AutoMapper REDACTED:8 — REDACTED → 16.2.0 available (referenced by BugTracker.Application).
  • Outdated: AutoMapper.Extensions.Microsoft.DependencyInjection REDACTED:9 — AutoMapper.Extensions.Microsoft.DependencyInjection 8.1.1 → 12.0.1 available (referenced by BugTracker.Application).
  • Outdated: MediatR REDACTED:13 — MediatR 9.0.0 → 14.2.0 available (referenced by BugTracker.Application).
  • Outdated: Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation REDACTED:15 — Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation 5.0.11 → 10.0.13 available (referenced by BugTracker).
  • Outdated: Microsoft.VisualStudio.Web.CodeGeneration.Design REDACTED:16 — Microsoft.VisualStudio.Web.CodeGeneration.Design 5.0.2 → 10.0.2 available (referenced by BugTracker).
IC1 · Incompleteness & stubs · Commented-out code · ×4
  • Commented-out code src/BugTracker.Application/Features/Audits/Queries/LogToViewHelper.cs:33 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/BugTracker.Infrastructure/InfrastructureServiceRegistration.cs:21 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/BugTracker.Infrastructure/InfrastructureServiceRegistration.cs:22 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/BugTracker.Infrastructure/InfrastructureServiceRegistration.cs:25 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
IC1 · Incompleteness & stubs · Placeholder data left in code · ×4
  • Placeholder data left in code src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:29 — A placeholder value ("John doe") is still in shipped code — sample/mock data that was never replaced with the real thing.
  • Placeholder data left in code src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:30 — A placeholder value ("JOHN DOE") is still in shipped code — sample/mock data that was never replaced with the real thing.
  • Placeholder data left in code src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:42 — A placeholder value ("Jane doe") is still in shipped code — sample/mock data that was never replaced with the real thing.
  • Placeholder data left in code src/BugTracker.Persistence/Configurations/Identity/UserConfiguration.cs:43 — A placeholder value ("JANE DOE") is still in shipped code — sample/mock data that was never replaced with the real thing.
S1 · Web-Security Posture · No security response headers detected · ×2
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected src/WebApp/BugsTracker/Program.cs:22 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
X9 · Subsumed condition operand · Subsumed condition operand · ×2
  • Subsumed condition operand src/BugTracker.Persistence/IdentityServiceExtension.cs:83 — `c.Value.Contains("Demo Admin")` can never decide this `||` — every value satisfying `c.Value.Contains("Demo Admin")` also satisfies `c.Value.Contains("Admin")`, 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.
  • Subsumed condition operand src/BugTracker.Persistence/IdentityServiceExtension.cs:83 — `c.Value.Contains("Demo Project Manager")` can never decide this `||` — every value satisfying `c.Value.Contains("Demo Project Manager")` also satisfies `c.Value.Contains("Project Manager")`, 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.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IIdentityService (25 members) src/BugTracker.Application/Contracts/Identity/IIdentityService.cs:12 — `IIdentityService` declares 25 members: `AddUserToRole`, `AuthenticateAsync`, `ConfirmEmail`, `CountManageableUsers`, `DeleteUserAsync`, `GeneratePasswordForgottenMailToken`, `GenerateRegistrationEncodedToken`, `GetAccessibleTicketTeam`, `GetAllAccessibleUsersPerRole`, `GetAllManageableUsers`, `GetCurrentTicketTeam`, `GetUserNameById`, `GetUserOrNullAsync`, `GetUserRolesById`, `ListAllRoles`, `LockOutUser`, `Register`, `RemoveUserFromRole`, `ResetPassword`, `SignOutAsync`, `UnlockUser`, `UpdateUserRoles`, `UserEmailExist`, `UserIdExists`, `UsernameExist`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Split BugTracker.Application · ×1
  • Split BugTracker.Application — A generic catch-all name that is huge (3k LoC) and sprawls across 56 namespaces with no coherent theme. Suggested:
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 29 of 29 significant files have no living knowledge — the codebase as a whole is dormant, not 29 separate risks. Counted over 29 of the 174 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D34 · Knowledge Freshness · Most significant orphaned file · ×1
  • Most significant orphaned file src/BugTracker.Persistence/Services/Data/TicketRepository.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D39 · IL Efficiency · IL efficiency · ×1
  • IL efficiency: 2 authored method(s) exceed the IL budget src/BugTracker.Application/Profiles/MappingProfile.cs:31 — 2 of 387 first-party methods compile to oversized IL bodies (> 250 instructions); worst: BugTracker.Application.Profiles.MappingProfile..ctor @ src/BugTracker.Application/Profiles/MappingProfile.cs:31, 385 IL instructions; that pulled this dimension to 9.9/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
D9 · Test Distribution · No tests found · ×1
  • No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 39/158 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/5 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Minor — 14 finding(s)
D12 · Dependency Hygiene · Outdated · ×9
  • Outdated: Newtonsoft.Json — Newtonsoft.Json 13.0.1 → 13.0.4 available (referenced by BugTracker.Persistence).
  • Outdated: SendGrid — SendGrid 9.24.1 → 9.29.3 available (referenced by BugTracker.Infrastructure).
  • Outdated: FluentValidation — FluentValidation 10.3.6 → 12.2.0 available (referenced by BugTracker.Application).
  • Outdated: FluentValidation.AspNetCore — FluentValidation.AspNetCore 10.3.4 → 11.3.1 available (referenced by BugTracker.Application).
  • Outdated: FluentValidation.DependencyInjectionExtensions — FluentValidation.DependencyInjectionExtensions 10.3.4 → 12.2.0 available (referenced by BugTracker.Application).
  • Outdated: MediatR.Extensions.Microsoft.DependencyInjection — MediatR.Extensions.Microsoft.DependencyInjection 9.0.0 → 11.1.0 available (referenced by BugTracker.Application).
  • Outdated: Azure.Extensions.AspNetCore.Configuration.Secrets — Azure.Extensions.AspNetCore.Configuration.Secrets 1.0.0 → 1.5.2 available (referenced by BugTracker).
  • Outdated: Azure.Identity — REDACTED → 1.21.0 available (referenced by BugTracker).
  • Outdated: Microsoft.AspNetCore.Mvc.Core — Microsoft.AspNetCore.Mvc.Core 2.2.5 → 2.3.13 available (referenced by BugTracker).
D19 · Documentation Quality · XML-doc coverage · ×5
  • XML-doc coverage: BugTracker.Domain src/BugTracker.Domain/BugTracker.Domain.csproj — BugTracker.Domain: 0 % XML-doc coverage (0/65).
  • XML-doc coverage: BugTracker.Persistence REDACTED — BugTracker.Persistence: 0 % XML-doc coverage (0/134).
  • XML-doc coverage: BugTracker.Infrastructure REDACTED — BugTracker.Infrastructure: 0 % XML-doc coverage (0/8).
  • XML-doc coverage: BugTracker.Application REDACTED — BugTracker.Application: 0 % XML-doc coverage (0/476).
  • XML-doc coverage: BugTracker REDACTED — BugTracker: 0 % XML-doc coverage (0/72).

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3819ed56364544df94723654be68e518/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3819ed56364544df94723654be68e518/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .9artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list BugTracker.sln package --vulnerable --include-transitive --format json9artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

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

Email — 6 field(s)
  • AuthenticationModel.Email src/BugTracker.Application/Model/Identity/Authentication/AuthenticationModel.cs:10
  • EmailConfirmationModel.Email src/BugTracker.Application/Model/Identity/ConfirmationAndReset/EmailConfirmationModel.cs:5
  • ForgotPasswordModel.Email src/BugTracker.Application/Model/Identity/ConfirmationAndReset/ForgotPasswordModel.cs:8
  • RegistrationModel.Email src/BugTracker.Application/Model/Identity/Registration/RegistrationModel.cs:10
  • UserViewModel.Email src/BugTracker.Application/ViewModel/UserViewModel.cs:8
  • EmailService._emailSettings src/BugTracker.Infrastructure/Mail/EmailService.cs:15
Name — 6 field(s)
  • RegistrationModel.FirstName src/BugTracker.Application/Model/Identity/Registration/RegistrationModel.cs:14
  • RegistrationModel.LastName src/BugTracker.Application/Model/Identity/Registration/RegistrationModel.cs:18
  • UserViewModel.FirstName src/BugTracker.Application/ViewModel/UserViewModel.cs:9
  • UserViewModel.LastName src/BugTracker.Application/ViewModel/UserViewModel.cs:10
  • ApplicationUser.FirstName src/BugTracker.Domain/Identity/ApplicationUser.cs:9
  • ApplicationUser.LastName src/BugTracker.Domain/Identity/ApplicationUser.cs:10

Issues: 72 · Warnings: 218 · Recommendations: 64 · Info: 14 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 22:05 UTC.

Downloadable artifacts

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

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