microsoft/ailab

Executive summary

microsoft/ailab scores 28 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 16 and is rated Critical. Its Test 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 3 No assertions finding(s) in Test Quality and to resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life, and if Production Readiness rose to 70, the score would rise from 28 to about 37.

128 findings are critical: 48 in Explicit Debt, 20 in Text alternatives, 18 in Forms & labels, 17 in Dependency Vulnerabilities, six in Page structure, six in Static Analysis (SAST), three in Circular Imports, three in IaC & Container Security, three in Project dependency cycles, two in Keyboard semantics, one in Dependency Hygiene and one in Web-Security Posture.

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

Code Health 42 Weak, capped by Solution Shape, Structured logging and Nullable reference types Architecture 72 Adequate, capped by Circular Imports Maturity 53 Adequate, capped by Knowledge Freshness Production Readiness 16 ⚠ Critical, capped by Test Coverage, Tooling, CI/CD gates, Security & performance tooling and Outbound HTTP resilience Security and Compliance 27 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities, IaC & Container Security, Platform End-of-Life, Access Controls and Web-Security Posture Accessibility 39 Weak, capped by Keyboard semantics Performance 85 Strong

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

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

Production Readiness 16 · counts for 46%Security and Compliance 27 · counts for 25%Accessibility 39 · counts for 14%Code Health 42 · counts for 8%Maturity 53 · counts for 4%Architecture 72 · counts for 2%Performance 85 · counts for 1%

If Production Readiness rose from 16 to 70, the lowest score rated Strong, the score would rise from 28 to about 37.

Code composition: what the lines of code are

Business logic 31%Supporting code 61%Tests 2%Generated by tools 6%

New since the last survey: 92 findings

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

Explicit Debt · EmptyCatchBlock Snip-Insights/SnipInsight/Util/Diagnostics.cs
Explicit Debt · EmptyCatchBlock Snip-Insights/SnipInsight/Util/Diagnostics.cs
Explicit Debt · EmptyCatchBlock Snip-Insights/SnipInsight/Util/Diagnostics.cs
Explicit Debt · EmptyCatchBlock VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Access Controls · No authorization BuildAnIntelligentBot/src/ChatBot/Controllers/BotController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/ErrorController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Access Controls · No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Async correctness · Blocking `StreamReader.ReadToEnd` inside an `async` method Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs
Async correctness · Sync-over-async (deadlock risk) through `.Result` Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs
Async correctness · Sync-over-async (deadlock risk) through `.Result` Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs
Async correctness · Sync-over-async (deadlock risk) through `Task.WaitAny` BuildAnIntelligentBot/src/ChatBot/Services/TranslatorSpeechService.cs
Async correctness · Blocking `StreamReader.ReadToEnd` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs
Async correctness · Blocking `StreamReader.ReadToEnd` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs
Async correctness · Blocking `StreamReader.ReadToEnd` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs
Async correctness · Blocking `Thread.Sleep` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs
Cancellation propagation · Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs
Cancellation propagation · Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/ImageSearchHandler.cs
Cancellation propagation · Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/ProductSearchHandler.cs
Exception handling · Swallowed exception (caught, then discarded) Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs
Exception handling · Swallowed exception (caught, then discarded) Snip-Insights/SnipInsight/Util/AppUsageLogger.cs
Exception handling · Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/Diagnostics.cs
Exception handling · Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/Diagnostics.cs
Exception handling · Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/Diagnostics.cs
Exception handling · Swallowed exception (empty catch) VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs
Incompleteness & stubs · Empty method body — does nothing with its inputs Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs
Incompleteness & stubs · Empty method body — does nothing with its inputs Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs
Incompleteness & stubs · Empty method body — does nothing with its inputs Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs
Incompleteness & stubs · Hollow method — returns a constant without doing the work Snip-Insights/SnipInsight/Views/ControlTreeEnumerator.cs
Incompleteness & stubs · Markup wires an event to an empty handler Snip-Insights/SnipInsight/Views/SettingsPanel.xaml.cs
Outbound HTTP resilience · Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/AzureAuthenticationService.cs
Outbound HTTP resilience · Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs
Outbound HTTP resilience · Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs
Outbound HTTP resilience · Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs
Outbound HTTP resilience · Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Utils/AudioUtils.cs
Outbound HTTP resilience · Outbound HTTP without resilience JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs
Outbound HTTP resilience · Outbound HTTP without resilience Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Outbound HTTP resilience · Outbound HTTP without resilience Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Outbound HTTP resilience · Outbound HTTP without resilience Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs
Outbound HTTP resilience · Outbound HTTP without resilience Snip-Insights/SnipInsight/AIServices/CloudService.cs
Outbound HTTP resilience · Outbound HTTP without resilience Snip-Insights/SnipInsight/Util/LogUploader.cs
Outbound HTTP resilience · Outbound HTTP without resilience VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/AppUpdaterService.cs
Visual & motion safety · Animation without a prefers-reduced-motion guard GoogleAssistantConnector/DemoBot/BotUsingCards/wwwroot/default.htm
Visual & motion safety · Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap-reboot.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement JFKFiles/frontend/src/pages/home-page/components/search/search-input.style.scss
Visual & motion safety · Focus outline removed in CSS without a :focus replacement BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Visual & motion safety · Animation without a prefers-reduced-motion guard Sketch2Code/Sketch2Code.Web/Content/bootstrap.css
Visual & motion safety · Animation without a prefers-reduced-motion guard JFKFiles/frontend/src/pages/search-page/components/page-bar/view-mode-toggler.style.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard JFKFiles/frontend/src/pages/search-page/components/drawer/drawer.style.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard JFKFiles/frontend/src/common/components/chevron/chevron.style.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/styles/app.css
Visual & motion safety · Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Visual & motion safety · Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Visual & motion safety · Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Visual & motion safety · Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Visual & motion safety · Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css
Async & latency hygiene · Sync-over-async blocking
Async & latency hygiene · Sync-over-async blocking VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs

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

Fixed since the last survey: 126 findings

These 126 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one. The first 100 are listed here.

Coupling · Off the main sequence: Speaker.Recorder.UWP.Controls
Dependency Hygiene · Vulnerable: Newtonsoft.Json
Dependency Hygiene · Vulnerable: Refit
Dependency Hygiene · Vulnerable: SixLabors.ImageSharp
Dependency Hygiene · Vulnerable: Microsoft.NETCore.App
Dependency Hygiene · Vulnerable: System.Net.Http
Dependency Hygiene · Vulnerable: System.Text.RegularExpressions
Dependency Hygiene · Vulnerable: Microsoft.Data.OData
Dependency Hygiene · Vulnerable: Microsoft.AspNetCore.All
Dependency Hygiene · Deprecated: Xam.Plugins.Settings
Dependency Hygiene · Deprecated: Microsoft.NETCore.App
Dependency Hygiene · Deprecated: xunit
Dependency Hygiene · Deprecated: SixLabors.Core
Dependency Hygiene · Deprecated: MvvmLightLibs
Dependency Hygiene · Deprecated: AsyncUsageAnalyzers
Dependency Hygiene · Deprecated: Microsoft.AspNetCore
Dependency Hygiene · Deprecated: Microsoft.AspNetCore.All
Dependency Hygiene · Deprecated: Microsoft.Bot.Builder
Dependency Hygiene · Deprecated: Microsoft.Bot.Builder.Integration.AspNet.Core
Dependency Hygiene · Deprecated: Microsoft.Bot.Configuration
Dependency Hygiene · Deprecated: Microsoft.Bot.Connector
Dependency Hygiene · Deprecated: Microsoft.Bot.Schema
Dependency Hygiene · Deprecated: Microsoft.Extensions.Logging.AzureAppServices
Dependency Hygiene · Deprecated: Microsoft.Azure.Search
Dependency Hygiene · Deprecated: Microsoft.NET.Sdk.Functions
Dependency Hygiene · Deprecated: Microsoft.Bot.Builder.Dialogs
Dependency Hygiene · Prerelease dependency: SixLabors.ImageSharp
Dependency Hygiene · Prerelease dependency: Microsoft.NET.Test.Sdk
Dependency Hygiene · Prerelease dependency: SixLabors.Core
Dependency Hygiene · Prerelease dependency: System.Memory
Dependency Hygiene · Prerelease dependency: System.Runtime.CompilerServices.Unsafe
Dependency Hygiene · Prerelease dependency: AsyncUsageAnalyzers
Dependency Hygiene · Prerelease dependency: Microsoft.Bot.Builder.PersonalityChat
Dependency Hygiene · Prerelease dependency: StyleCop.Analyzers
Static Analysis (SAST) · Medium: watchdog-controllerbase-missing-or-broken-authorization-csharp BuildAnIntelligentBot/src/ChatBot/Controllers/BotController.cs
Async correctness · Sync-over-async (deadlock risk) JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs
Cancellation propagation · Async method without CancellationToken: GetResult Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs
Cancellation propagation · Async method without CancellationToken: GetLanguagesForTranslate Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs
Cancellation propagation · Async method without CancellationToken: GetLanguageNames Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs
Cancellation propagation · Async method without CancellationToken: CreateAndOpenICSFile Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs
Cancellation propagation · Async method without CancellationToken: DeleteAsync Snip-Insights/SnipInsight/AppManager.cs
Cancellation propagation · Async method without CancellationToken: GetPackageDataAsync Snip-Insights/SnipInsight/Package/SnipInsightsManager.cs
Cancellation propagation · Async method without CancellationToken: CheckUploadStatusAsync VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs
Cancellation propagation · Async method without CancellationToken: UploadAsync VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs
Cancellation propagation · Async method without CancellationToken: Start VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/PowerPointRecorderService.cs
Cancellation propagation · Async method without CancellationToken: InitializeContainerAsync VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/UploadManager.cs
Cancellation propagation · Async method without CancellationToken: GetUploadedDateTime VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/UploadManager.cs
Cancellation propagation · Async method without CancellationToken: GetJournalStream VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/UploadManager.cs
Cancellation propagation · Async method without CancellationToken: GetDirectoryBlobAsync VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/UploadManager.cs
Cancellation propagation · Async method without CancellationToken: AcceptStopUploadDialog VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs
Cancellation propagation · Async method without CancellationToken: PauseUpload VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs
Cancellation propagation · Async method without CancellationToken: PlayUpload VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs
Cancellation propagation · Async method without CancellationToken: Upload VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs
Cancellation propagation · Async method without CancellationToken: KinectDeviceCountUpdater VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/RecordViewModel.cs
Cancellation propagation · Async method without CancellationToken: AceptsEmptyDialog VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/RecordViewModel.cs
Cancellation propagation · Async method without CancellationToken: SetVideos VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/VideosPlayer.xaml.cs
Cancellation propagation · Async method without CancellationToken: assignPredictedText Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs
Cancellation propagation · Async method without CancellationToken: SaveHtmlResults Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs
Cancellation propagation · Async method without CancellationToken: GetFile Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs
Cancellation propagation · Async method without CancellationToken: GetProjectAsync Sketch2Code/Sketch2Code.AI/CustomVisionClient.cs
Cancellation propagation · Async method without CancellationToken: GetIterations Sketch2Code/Sketch2Code.AI/CustomVisionClient.cs
Cancellation propagation · Async method without CancellationToken: SetDefaultIterationAsync Sketch2Code/Sketch2Code.AI/CustomVisionClient.cs
Cancellation propagation · Async method without CancellationToken: CreateProject Sketch2Code/Sketch2Code.AI/Management/CustomVisionManager.cs
Cancellation propagation · Async method without CancellationToken: GetProject Sketch2Code/Sketch2Code.AI/Management/CustomVisionManager.cs
Cancellation propagation · Async method without CancellationToken: CreateTag Sketch2Code/Sketch2Code.AI/Management/CustomVisionManager.cs
Cancellation propagation · Async method without CancellationToken: GetTags Sketch2Code/Sketch2Code.AI/Management/CustomVisionManager.cs
Cancellation propagation · Async method without CancellationToken: GetImagesForTraining Sketch2Code/Sketch2Code.AI/Management/CustomVisionManager.cs
Cancellation propagation · Async method without CancellationToken: CreateDataset Sketch2Code/Sketch2Code.AI/Management/CustomVisionManager.cs
Cancellation propagation · Async method without CancellationToken: GetDetectedObjects Sketch2Code/Sketch2Code.AI/ObjectDetector.cs
Cancellation propagation · Async method without CancellationToken: GetText Sketch2Code/Sketch2Code.AI/ObjectDetector.cs
Cancellation propagation · Async method without CancellationToken: GetTextRecognition Sketch2Code/Sketch2Code.AI/ObjectDetector.cs
Cancellation propagation · Async method without CancellationToken: Run Sketch2Code/Sketch2Code.Api/ObjectDetection.cs
Cancellation propagation · Async method without CancellationToken: Index Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Step2 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Step2FromSample Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Step3 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Upload Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: callBackEndFunction Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: callBackEnd Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: saveResults Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: saveResults2 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Step4 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Step5 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: TakeSnapshot Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Details Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: File Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Loader1 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Loader2 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: SaveFile Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs
Cancellation propagation · Async method without CancellationToken: Details Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Cancellation propagation · Async method without CancellationToken: GroupBox Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Cancellation propagation · Async method without CancellationToken: Result Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Cancellation propagation · Async method without CancellationToken: RawGroupBox Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs
Cancellation propagation · Async method without CancellationToken: Index Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Cancellation propagation · Async method without CancellationToken: Uploader Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Cancellation propagation · Async method without CancellationToken: Details Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Cancellation propagation · Async method without CancellationToken: File Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Cancellation propagation · Async method without CancellationToken: FileJson Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs
Cancellation propagation · Async method without CancellationToken: PostAsync BuildAnIntelligentBot/src/ChatBot/Controllers/BotController.cs
Cancellation propagation · Async method without CancellationToken: PostPersonalityChatResponseToUserAsync BuildAnIntelligentBot/src/ChatBot/Middlewares/PersonalityChatMiddleware.cs

Rebuild cost: about €66,000 · Estimate

Cost to rebuild	€22,000 to €110,000, for 363 to 1,155 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 28. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 64,251 lines of product code
Comment lines	The estimate prices 60,753 lines. Comment lines count towards the size of 64,251 lines but aren't priced as work.

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

Top priorities

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

Resolve the 3 No assertions finding(s) in Test Quality — start with AITests.cs (2), ApplicationTests.cs.

Raises the score by about 4 points · Low effort · Test Quality

Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with SnipInsight.Forms.Tests.csproj, CardsBot.csproj, ChatBot.csproj.

Raises the score by about 2 points · Low effort · Platform End-of-Life

Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.

Raises the score by about 4 points · Medium effort · Access Controls

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.

If you do one thing first · First action

Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: MSB4018: The "Nerdbank.GitVersioning.Tasks.GetBuildVersion" task failed unexpectedly.; MSB4018: System.TypeInitializationException: The type initializer for 'LibGit2Sharp.Core.NativeMethods' threw an exception.; MSB4018: ---> System.DllNotFoundException: Unable to load shared library '/root/.nuget/packages/nerdbank.gitversioning/2.1.23/build/MSBuildFull/lib/linux/x86_64/libgit2-1196807.so' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:; MSB4018: libssl.so.1.0.0: cannot open shared object file: No such file or directory; MSB4018: [Snip-Insights/SnipInsight.Forms/SnipInsight.Forms.csproj]; MSB3073: The command "taskkill /IM "Snip Insights.exe" /FI "STATUS eq RUNNING" /F" exited with code 127.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/WindowsXaml/v18.0/Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath)/Microsoft/WindowsXaml/v$(VisualStudioVersion)/Microsoft.Windows.UI.Xaml.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400//Microsoft/WindowsXaml/v18.0/Microsoft.Windows.UI.Xaml.CSharp.targets", is correct, and that the file exists on disk.; CS0234: The type or namespace name 'PersonalityChat' does not exist in the namespace 'Microsoft.Bot.Builder' (are you missing an assembly reference?); CS0246: The type or namespace name 'PersonalityChatResults' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'PersonalityChatService' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'PersonalityChatMiddlewareOptions' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Azure' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0234: The type or namespace name 'WindowsAzure' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ISearchServiceClient' could not be found (are you missing a using directive or an assembly reference?)

Based on: Solution Shape

Where the investment is most exposed · Value at risk

This code would cost about €66,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 16 (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.

Architecture — bounded-context dependency graph

Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.

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.

219 modules, with 173 dependencies between them. 3 loops run through 6 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 179 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 ChatBot.Models	2 JFKFiles.frontend.src.az-api.payload.filter_model	3 JFKFiles.frontend.src.az-api.response_model	4 JFKFiles.frontend.src.common.components.hocr.hocr-document.hocr-document_style	5 JFKFiles.frontend.src.common.components.hocr.hocr-preview.hocr-preview_style	6 JFKFiles.frontend.src.common.components.hocr.hocr-preview.rectangleProps	7 JFKFiles.frontend.src.common.components.hocr.util.common-util	8 JFKFiles.frontend.src.graph-api.config_model	9 JFKFiles.frontend.src.graph-api.response_model	10 JFKFiles.frontend.src.pages.search-page.view-model.facet_model	11 JFKFiles.frontend.src.pages.search-page.view-model.filter_model	12 JFKFiles.frontend.src.pages.search-page.view-model.item_model	13 JFKFiles.frontend.src.pages.search-page.view-model.suggestion_model	14 SnipInsight.AIServices.AILogic	15 SnipInsight.Util	18 JFKFiles.frontend.src.az-api.payload.payload_model	19 JFKFiles.frontend.src.common.components.hocr.hocr-preview.hocr-page_component	22 JFKFiles.frontend.src.pages.search-page.view-model.state_model	23 Sketch2Code.Core.Entities	24 SnipInsight.AIServices.AIViewModels	25 SnipInsight.Views	31 JFKFiles.frontend.src.pages.search-page.service.service_model	32 Sketch2Code.Core.BoxGeometry	33 SnipInsight.ViewModels	34 JFKFiles.frontend.src.pages.search-page.search-page_component	36 Sketch2Code.Core.Services.Interfaces	37 SnipInsight	39 Sketch2Code.Core
1 ChatBot.Models
2 JFKFiles.frontend.src.az-api.payload.filter_model
3 JFKFiles.frontend.src.az-api.response_model
4 JFKFiles.frontend.src.common.components.hocr.hocr-document.hocr-document_style
5 JFKFiles.frontend.src.common.components.hocr.hocr-preview.hocr-preview_style
6 JFKFiles.frontend.src.common.components.hocr.hocr-preview.rectangleProps
7 JFKFiles.frontend.src.common.components.hocr.util.common-util
8 JFKFiles.frontend.src.graph-api.config_model
9 JFKFiles.frontend.src.graph-api.response_model
10 JFKFiles.frontend.src.pages.search-page.view-model.facet_model
11 JFKFiles.frontend.src.pages.search-page.view-model.filter_model
12 JFKFiles.frontend.src.pages.search-page.view-model.item_model
13 JFKFiles.frontend.src.pages.search-page.view-model.suggestion_model
14 SnipInsight.AIServices.AILogic
15 SnipInsight.Util
16 Speaker.Recorder.Services
17 ChatBot.Services	2
18 JFKFiles.frontend.src.az-api.payload.payload_model		1
19 JFKFiles.frontend.src.common.components.hocr.hocr-preview.hocr-page_component					1	2
20 JFKFiles.frontend.src.graph-api								3	5
21 JFKFiles.frontend.src.pages.search-page.components.graph.graph-view_component								2	1
22 JFKFiles.frontend.src.pages.search-page.view-model.state_model										1	1	1	1
23 Sketch2Code.Core.Entities																							1
24 SnipInsight.AIServices.AIViewModels														7
25 SnipInsight.Views															6												1
26 JFKFiles.frontend.src.az-api			3													1
27 JFKFiles.frontend.src.az-api.payload		3														2
28 JFKFiles.frontend.src.common.components.hocr.hocr-preview					1	1											1
29 JFKFiles.frontend.src.common.components.hocr.hocr-preview.hocr-preview_component					2		3										1
30 JFKFiles.frontend.src.common.components.hocr.hocr-proofreader.hocr-proofreader_component				1	1		2										1
31 JFKFiles.frontend.src.pages.search-page.service.service_model			1					1								1
32 Sketch2Code.Core.BoxGeometry																			5
33 SnipInsight.ViewModels																				5
34 JFKFiles.frontend.src.pages.search-page.search-page_component										1	1	1	1					1				1
35 JFKFiles.frontend.src.pages.search-page.service.jfk		3	5							3	2	2	1			2		2				2
36 Sketch2Code.Core.Services.Interfaces																			2				1
37 SnipInsight														1	1						3			1
38 JFKFiles.frontend.src.pages.search-page											1		1					2							1
39 Sketch2Code.Core																			2				1			1
40 Sketch2Code.Web.Controllers																			1				1			3		1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 42% · Weak · gated by D18, X4, X5 ·

The Good

D1 · .NET / C# Cyclomatic Complexity 7.0 D3 · .NET / C# God Classes 9.0 D4 · .NET / C# Code Duplication 9.1 GD1 · Repo Unfinished & placeholder code 9.8 R1 · React / TS Type Safety 8.5 R10 · React / TS Code Duplication 8.8 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 9.7 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0

The Bad

D2 · .NET / C# Cognitive Complexity 6.2 D17 · .NET / C# Explicit Debt 5.9 IC1 · Repo Incompleteness & stubs 6.9 X1 · Repo Async correctness 5.3 X18 · Repo Disposal-pattern correctness 5.5 X3 · Repo Exception handling 5.3

The Ugly

D18 · .NET / C# Solution Shape 3.0 X2 · Repo Cancellation propagation 4.5 X20 · Repo Mistyped argument guard 3.6 X4 · Repo Structured logging 2.0 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 72% · Adequate · gated by R9 ·

The Good

D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 9.0 D22 · .NET / C# Internal API Consistency 10.0 D26 · .NET / C# Project Cohesion 8.5 D27 · .NET / C# Navigability 9.0 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 9.7 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0

The Bad

AX2 · Repo Stateful singletons 5.3

The Ugly

R9 · React / TS Circular Imports 3.6

At a glance — Maturity · 53% · Adequate · gated by D34 ·

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 8.0 D21 · .NET / C# Naming Consistency 8.5 D24 · .NET / C# Comment Value 9.4 M4 · Repo Documentation accuracy 9.7

The Bad

M1 · Repo Documentation (README) 6.3 M2 · Repo Architecture documentation 5.0

The Ugly

D20 · .NET / C# ADR Quality 0.0 D34 · .NET / C# Knowledge Freshness 0.0 M3 · Repo Folder & project structure 4.0

At a glance — Readiness · 16% · Critical · gated by R4, R6, P1, P3, P7 ·

The Good

D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 8.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 R5 · React / TS Dependency Freshness 9.9 R8 · React / TS Dependency Hygiene 8.0

The Bad

P2 · Repo Observability 6.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0

The Ugly

P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P7 · Repo Outbound HTTP resilience 3.0 R4 · React / TS Test Coverage 0.0 R6 · React / TS Tooling 0.0

At a glance — Security · 27% · Weak · gated by D29, D30, D31, D44, C2, S1 ·

The Good

D28 · .NET / C# Secrets (history) 10.0 D37 · .NET / C# Vulnerability-disclosure Policy 10.0 D43 · .NET / C# Malicious Dependencies 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0

The Bad

D40 · .NET / C# Network Egress Confinement 6.0 D41 · .NET / C# Kernel & Syscall Confinement 6.0 C1 · Repo Data Protection 6.5

The Ugly

D29 · .NET / C# Static Analysis (SAST) 0.7 D30 · .NET / C# Dependency Vulnerabilities 0.0 D31 · .NET / C# IaC & Container Security 2.5 D44 · .NET / C# Platform End-of-Life 2.0 C2 · Repo Access Controls 0.0 S1 · Repo Web-Security Posture 2.0 X24 · Repo Document value interpolated into markup unescaped 3.1

At a glance — Accessibility · 39% · Weak · gated by AC4 ·

The Good

AC5 · Repo ARIA correctness 10.0

The Bad

AC1 · Repo Text alternatives 5.1 AC2 · Repo Forms & labels 5.2 AC3 · Repo Page structure 5.2

The Ugly

AC4 · Repo Keyboard semantics 1.0 AC6 · Repo Visual & motion safety 4.5 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 85% · Strong ·

The Good

PF3 · Repo Async & latency hygiene 8.5

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A02:2025 — Security Misconfiguration	59	High / Critical
A05:2025 — Injection	34	High / Critical
A03:2025 — Software Supply Chain Failures	28	High / Critical

Roadmap

Begin by fixing the three missing assertions in the test files to establish a baseline for test quality. Next, secure the application by implementing default-deny access controls on all endpoints and moving cryptographic secrets out of source code into configuration or a secrets manager. Finally, introduce a CI pipeline that automatically runs the test suite and security analysis tools on every change to prevent regressions from reaching production.

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

Do this	Helps	Effort	Dimension
Resolve the 3 No assertions finding(s) in Test Quality — start with AITests.cs (2), ApplicationTests.cs.	+4.5 pts	Low	Test Quality
Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with SnipInsight.Forms.Tests.csproj, CardsBot.csproj, ChatBot.csproj.	+2.3 pts	Low	Platform End-of-Life
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.	+4.1 pts	Medium	Access Controls
Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.	+3.6 pts	Medium	Web-Security Posture
Add a CI workflow that builds and runs the test suite on every push/PR.	+3.0 pts	Medium	CI/CD gates
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.	+3.0 pts	Medium	Security & performance tooling
Add tests that import the unreached modules (directly or through their public entry).	+3.0 pts	Medium	Test Coverage
Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.	+3.0 pts	Medium	Tooling

File quality

Per-file score 0–10 — a quality signature. Of 115 files carrying findings, judged against the Production bar: 7% slop · 57% mixed · 36% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
Snip-Insights/SnipInsight/AppManager.cs	1.0	Slop	Explicit Debt: EmptyCatchBlock
REDACTED	1.6	Slop	IaC & Container Security: High IaC: REDACTED
Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs	1.7	Slop	Explicit Debt: EmptyCatchBlock
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	Explicit Debt: EmptyCatchBlock
REDACTED	2.7	Slop	IaC & Container Security: High IaC: REDACTED
Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs	2.9	Slop	Explicit Debt: WriteOnlyPrivateField
REDACTED	4.0	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	4.2	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	4.3	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.8	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	5.1	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	5.1	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
Snip-Insights/SnipInsight/Util/AppUsageLogger.cs	5.2	Mixed	Explicit Debt: EmptyCatchBlock
Snip-Insights/SnipInsight/Util/RegistrySettings.cs	5.3	Mixed	Explicit Debt: EmptyCatchBlock
VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs	5.4	Mixed	Explicit Debt: WriteOnlyPrivateField
VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs	5.4	Mixed	Explicit Debt: EmptyCatchBlock
Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs	5.4	Mixed	Explicit Debt: WriteOnlyPrivateField
REDACTED	5.4	Mixed	Static Analysis (SAST): Medium: REDACTED

How the grades work

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

Critical — 128

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

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

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

Could not be resolved — 8

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

Methodology & how to trust this report

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

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

What we checked — 97 dimensions across the health lenses

D1D2D3D4D5D6D9D10D13D14D15D17D18D19D20D21D22D24D26D27D28D29D30D31D34D35D37D40D41D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8C1C2GD1IC1M1M2M3M4P1P2P3P4P6P7PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16809-1366-7c6b-889c-93c92e1db139.

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.

D11 Test Reliability — 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. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: error: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/WindowsXaml/v18.0/Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath)/Microsoft/WindowsXaml/v$(VisualStudioVersion)/Microsoft.Windows.UI.Xaml.CSh….
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Every one of the 162 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Snip-Insights/SnipInsight/SnipInsight.csproj' with message: The "Nerdbank.GitVersioning.Tasks.GetBuildVersion" task failed unexpectedly. System.TypeInitializationException: The type initializer for 'LibGit2Sharp.Core.NativeMethods' threw an exception. ---> System.DllNotFoundException: Unable to ….
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A scan loads every live solution in the repository into one workspace. Every score, lens, and finding here reflects the projects of `Snip-Insights/SnipInsights.GTK.sln`, `Snip-Insights/SnipInsights.GTK.MacOS.sln`, `Snip-Insights/SnipInsights.WPF.sln`, `VirtualStage/Speaker.Recorder/Speaker.Recorder.sln`, `Sketch2Code/Sketch2Code.sln`, `BuildAnIntelligentBot/src/TalkToMyBot.sln`, `JFKFiles/JfkWebApiSkills/JfkWebApiSkills.sln`, `GoogleAssistantConnector/DemoBot/DemoBot.sln`; 2 further solution(s) found in this tree (`GoogleAssistantConnector/GoogleAssistant/GoogleAssistantProxy.sln`, `Snip-Insights/SnipInsights.GTK.MacOS.sln`) could not be added to it — their project list could not be read, or none of their projects opened — so their code is not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed ones — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: if one of these solutions is live code, check that it opens on its own (`dotnet build <solution>`); if it is archived or vendored, declare it so.
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 (29,477 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `JFKFiles/JfkWebApiSkills/JfkInitializer/skillset.json`, `JFKFiles/JfkWebApiSkills/JfkInitializer/indexer.json`, `JFKFiles/JfkWebApiSkills/JfkInitializer/index.json`, `GoogleAssistantConnector/DemoBot/BotUsingCards/appsettings.json`, `BuildAnIntelligentBot/src/ChatBot/appsettings.json` and 2 more did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D31 IaC & Container Security — 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. REDACTED carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 2 of 3 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.js`, `JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped.
ED5 Idempotency — 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. This check reads a handler's ENTRY METHODS to decide whether its mutation is safe to re-run. On these types it walked none of them, yet the same write oracle finds a persistent write in the type — so the mutation is there and the limit is in our entry-point recognition, not in the repository. Known shapes: a handler contract method implemented as an EXPLICIT INTERFACE IMPLEMENTATION, and a STATIC handler method (the Wolverine default).
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 64 further occurrence(s) are not listed individually; the score already reflects all 104.
P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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. 71 further occurrence(s) are not listed individually; the score already reflects all 111.
X4 Structured logging — 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity7.0 / 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.0 / 10 · rule-coverage 100% · ceiling Prevented

23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was jquery-3.0.0.defaultPrefilter at 45. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being KeyCombo.IsValidPrimaryKey at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Snip-Insights/SnipInsight/Util/KeyCombo.cs (KeyCombo.IsValidPrimaryKey at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

jquery-3.0.0.defaultPrefilter (cyclomatic 45)Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6660

background_matting_image.inference (cyclomatic 36)VirtualStage/BackgroundMatting/background_matting_image.py:31

jquery-3.0.0.jQuery.Callbacks (cyclomatic 30)Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:3197

jquery-3.0.0.slim.jQuery.Callbacks (cyclomatic 30)Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:3197

RichMessageLimitationsManager.compact (cyclomatic 28)GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:11

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

What to do

Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with jquery-3.0.0.defaultPrefilter (cyclomatic 45), background_matting_image.inference (cyclomatic 36). — 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 2 together lifts Cyclomatic Complexity from 7.0 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
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.

Do you agree with this assessment?

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

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

jquery-3.0.0.defaultPrefilter (cognitive 81)Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6660

background_matting_image.inference (cognitive 75)VirtualStage/BackgroundMatting/background_matting_image.py:31

jquery-3.0.0.ajaxConvert (cognitive 73)Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:8464

jquery-3.0.0.domManip (cognitive 51)Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5564

jquery-3.0.0.slim.domManip (cognitive 51)Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:5564

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

What to do

Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with jquery-3.0.0.defaultPrefilter (cognitive 81), background_matting_image.inference (cognitive 75), jquery-3.0.0.ajaxConvert (cognitive 73). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.

Do you agree with this assessment?

D3 · God Classes9.0 / 10Stronggated by 7 serious findings✓ Tool-verified

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

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

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

7 god class(es) detected.

FileTooLong: Scripts/jquery-3.0.0.js · ×4Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js

TooManyMethods: AppManager · ×3Snip-Insights/SnipInsight/AppManager.cs

What to do

Resolve the 4 FileTooLong finding(s) in God Classes — start with jquery-3.0.0.js, jquery-3.0.0.slim.js, AppManager.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with AppManager.cs, ToolWindow.xaml.cs, AnimationUtilities.cs. — One of this dimension's main actionable groups (3 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

54 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (7 lines × 2) · ×5Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:352

Duplicated block (16 lines × 2) · ×4VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/Controls/TypeConverterHelper.cs:35

Duplicated block (10 lines × 2) · ×4Sketch2Code/Sketch2Code.AI/ObjectDetector.cs:44

Duplicated block (6 lines × 2) · ×4Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:200

Duplicated block (12 lines × 2) · ×3Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:121

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

What to do

Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Geometry.cs, StateMachine.cs, ControllerHelper.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with TypeConverterHelper.cs, ImageSearchModel.cs, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ObjectDetector.cs, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
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.

Do you agree with this assessment?

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.0 / 10Stronggated by 6 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.0 / 10 · rule-coverage 100% · ceiling Verified

6 of 74 classes have LCOM4 above 3.

Low cohesion: MainWindow (LCOM4 10) · ×6Snip-Insights/SnipInsight/Views/MainWindow.xaml.cs:20

What to do

Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with MainWindow.xaml.cs (2), ToolWindow.xaml.cs, AppManager.cs. — One of this dimension's main actionable groups (6 warning-level).
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.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality8.0 / 10Strong✓ Tool-verified

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

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

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

0 skipped, 3 zero-assertion, 1 mock references across 23 tests.

No assertions: ShouldPredictImage · ×3Sketch2Code/Sketch2Code.Tests/AITests.cs:46

Mock framework: Moq

What to do

Resolve the 3 No assertions finding(s) in Test Quality — start with AITests.cs (2), ApplicationTests.cs. — One of this dimension's main actionable groups (3 warning-level).
Stand up a CI pipeline, then gate Test Quality 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: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt5.9 / 10Adequate✓ Tool-verified

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

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

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

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

WriteOnlyPrivateField · ×26BuildAnIntelligentBot/src/ChatBot/Dialogs/ReservationDialog.cs:24

EmptyCatchBlock · ×19BuildAnIntelligentBot/src/ChatBot/Services/TextToSpeechService.cs:32

NoWarnInCsproj · ×2Snip-Insights/SnipInsight.Forms/SnipInsight.Forms.csproj:4

NoWarnInCsproj repeated 10 times in 2 filesVirtualStage/Speaker.Recorder/Speaker.Recorder.UWP/Speaker.Recorder.UWP.csproj:26

TodoComment · ×22Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:170

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

What to do

Resolve the 26 WriteOnlyPrivateField finding(s) in Explicit Debt — start with AppUsageLogger.cs (7), Direct3D11Helper.cs (3), Startup.cs (2). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 19 EmptyCatchBlock finding(s) in Explicit Debt — start with RegistrySettings.cs (6), Diagnostics.cs (3), OCRViewModel.cs (2). — One of this dimension's main actionable groups (19 issue-level).
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with SnipInsight.Forms.csproj, SnipInsight.Forms.Tests.csproj. — One of this dimension's main actionable groups (2 issue-level).
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.

Do you agree with this assessment?

D18 · Solution Shape3.0 / 10Weak✓ 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 3.0 / 10 · rule-coverage 100% · ceiling Documented

13 projects, 299 source files, 29787 hand-written lines of code (29477 production / 310 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 1711 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 8 inter-project edges (build failed). Measured across 8 solutions loaded as one workspace: `Snip-Insights/SnipInsights.GTK.sln`, `Snip-Insights/SnipInsights.GTK.MacOS.sln`, `Snip-Insights/SnipInsights.WPF.sln`, `VirtualStage/Speaker.Recorder/Speaker.Recorder.sln`, `Sketch2Code/Sketch2Code.sln`, `BuildAnIntelligentBot/src/TalkToMyBot.sln`, `JFKFiles/JfkWebApiSkills/JfkWebApiSkills.sln`, `GoogleAssistantConnector/DemoBot/DemoBot.sln`.

Build failed

Solution references 2 projects that do not existSketch2Code/Sketch2Code.sln

What to do

Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Solution references 2 projects that do not exist finding(s) in Solution Shape — start with Sketch2Code.sln. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

The repository's root README is excellent at describing what AI Lab is and its nine projects with links to experiments. It also documents contributing (CLA) and has a strong overview of the project as a whole. The BuildAnIntelligentBot/README is an internal directory README that is well written for its tier, covering setup, environment requirements, and a detailed build-and-test process with many numbered steps and cross-references to the full architecture outline. All 18 README files are present and document their respective directories; none of them is flagged by any defect in this summary. The XML-doc coverage figures reflect what is visible: 406/1431 (28%) for the repository, with no individual file below 1%. (16 of 25 sampled documents could not be assessed: 1 of 2 evaluation groups failed.)

Documentation: no project overview · ×3README.md

XML-doc coverage: SnipInsight · ×11Snip-Insights/SnipInsight/SnipInsight.csproj

What to do

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

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

Do you agree with this assessment?

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyStrong◐ Sampled · advisory

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

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

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

2 naming inconsistencies across 200 sampled symbols.

The configuration setting for fallback endpoints is named inconsistently. The property uses the clean name 'FallbackEndpoints', while the backing field uses a redundant suffix '_fallbackEndpointsName'. The suffix 'Name' is unnecessary as the property itself identifies the setting, and it differs from the property name it backs.

Spelling inconsistency in the word 'scale'. The field '_scalor' is a misspelling of 'scalar' or 'scale', but given the type is `DpiScale`, it is clearly intended to be 'scale'. Additionally, the resource string 'Screenshot_saved' uses an underscore separator, while other resource strings like 'TrayIcon_BalloonTip_AppIsStillRunning_Title' use underscores, but the field name uses a camelCase prefix with an underscore, which is inconsistent with the general naming style of other private fields in the codebase (e.g., `_instance`, `_actions`). However, the primary issue is the typo 'scalor' vs 'scale'.

What to do

Resolve the 1 The configuration setting for fallback endpoints is named… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Spelling inconsistency in the word 'scale'. The field '_scalor' is a… finding(s) in Naming Consistency. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D22 · Internal API ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

0 API inconsistencies across 1 exposed types.

✓ On the Gold path — maintain.

Detailed fixes: d22_recommendation.md.

Do you agree with this assessment?

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

88 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion8.5 / 10Strong✓ 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 8.5 / 10 · rule-coverage 100% · ceiling Documented

1 of 13 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D27 · Navigability9.0 / 10Exemplary✓ Tool-verified

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

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

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.

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.7 / 10Critical✓ Tool-verified

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

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

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

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

36 finding(s): 0 critical, 8 high, 25 medium, 3 low. semgrep hit a parse error in 7 file(s) — `BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.js`, `JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts` (line 31, line 32, lines 87–88, …), `REDACTED` (lines 15–17), `Sketch2Code/Sketch2Code.Web/Maqueta/Step2.html` (line 68), `Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0-vsdoc.js`, … (+2 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security~~3.7~~ 2.5 / 10Critical✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 67% · ceiling Documented

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D34 · Knowledge 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

162 of 162 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Snip-Insights/SnipInsight/AppManager.cs. Counted over 162 of the 432 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×159Snip-Insights/SnipInsight/ViewModels/SnipInsightViewModel.cs:1

Most significant orphaned file · ×3Snip-Insights/SnipInsight/AppManager.cs:1

Dormant codebase

What to do

Resolve the 159 Orphaned file finding(s) in Knowledge Freshness — start with OCRViewModel.cs (2), Program.cs (2), MainWindow.xaml.cs (2). — One of this dimension's main actionable groups (159 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with AppManager.cs, NativeMethods.cs, RegistrySettings.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

D40 · Network Egress Confinement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.

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

0/2 network-egress controls present (network policy, egress restriction).

No network policy

What to do

Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D41 · Kernel & Syscall Confinement6.0 / 10Adequate✓ Tool-verified

What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.

Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.

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

0/1 workload(s) run every container under a seccomp profile; 0/1 declare an AppArmor/SELinux profile.

No seccomp profileREDACTED:2

What to do

Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

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

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

End-of-life runtime: .NET netcoreapp2.0 · ×5Snip-Insights/SnipInsight.Forms.Tests/SnipInsight.Forms.Tests.csproj:3

What to do

Resolve the 5 End-of-life runtime finding(s) in Platform End-of-Life — start with SnipInsight.Forms.Tests.csproj, CardsBot.csproj, ChatBot.csproj. — One of this dimension's main actionable groups (5 warning-level).

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives5.1 / 10Adequate✓ 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.

An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×20) — Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:78, Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:94, Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:105, …

What to do

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

Do you agree with this assessment?

AC2 · Forms & labels5.2 / 10Adequate✓ Tool-verified

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

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

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

This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. — JFKFiles/frontend/src/pages/home-page/components/search/search-input.component.tsx:25
This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — JFKFiles/frontend/src/pages/home-page/home-page.component.tsx:24
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×11) — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1237, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1276, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2710, …
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. (×4) — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1275, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2697, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:1275, …
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — Sketch2Code/Sketch2Code.Web/Views/Shared/_Label.cshtml:2, Sketch2Code/Sketch2Code.Web/Views/Template/Index.cshtml:13

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.

Do you agree with this assessment?

AC3 · Page structure5.2 / 10Adequate✓ 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) — BuildAnIntelligentBot/src/ChatBot/wwwroot/default.htm:2, JFKFiles/frontend/src/index.html:2, Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:7, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — BuildAnIntelligentBot/src/ChatBot/wwwroot/default.htm:2, Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:7
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×16) — BuildAnIntelligentBot/src/ChatBot/wwwroot/default.htm:2, GoogleAssistantConnector/DemoBot/BotUsingCards/wwwroot/default.htm:2, JFKFiles/frontend/src/index.html:2, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×3) — Sketch2Code/Sketch2Code.Web/Maqueta/Index.html:85, Sketch2Code/Sketch2Code.Web/Maqueta/IndexCarrousel.html:170, Sketch2Code/Sketch2Code.Web/Views/App/Index.cshtml:85

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.

Do you agree with this assessment?

AC4 · Keyboard semantics1.0 / 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".

This <rect> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. — JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-svg.component.tsx:25
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. — JFKFiles/frontend/src/pages/search-page/components/item/item.component.tsx:52

What to do

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

Do you agree with this assessment?

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

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

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

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

Do you agree with this assessment?

AC6 · Visual & motion safety4.5 / 10Weak✓ Tool-verified

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

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

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

`.ms-logo-container` moves (`transition: bottom 400ms`) 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. — GoogleAssistantConnector/DemoBot/BotUsingCards/wwwroot/default.htm:205
`header` sets color: white on background-color: #55A0E0 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — GoogleAssistantConnector/DemoBot/BotUsingCards/wwwroot/default.htm:8
`.btn-outline-info:not(:disabled):not(.disabled):active, .btn-outline-info:not(:disabled):not(.disabled).active, .show > .btn-outline-info.dropdown-toggle` sets color: #fff on background-color: #17a2b8 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:2761
`#steps .dot` sets color: #47445a on background-color: grey — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Sketch2Code/Sketch2Code.Web/Content/main.css:94
`#applyBtn, #submit-audio` sets color: white on background-color: #0078d7 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — BuildAnIntelligentBot/src/ChatBot/wwwroot/styles/app.css:79
`.wc-app button` sets color: #ffffff on background-color: #0078d7 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:6
`a:not([href]):not([tabindex]):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. (×2) — Sketch2Code/Sketch2Code.Web/Content/bootstrap-reboot.css:156, Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:186
`.btn.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. — Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:2343
`.custom-range: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. — Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:3727
`.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5316
`.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5370
`.carousel-control-prev: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. — Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5908
`.container .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. — JFKFiles/frontend/src/pages/home-page/components/search/search-input.style.scss:25
`.wc-message-groups` 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. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:48
`.wc-console input[type=text]` 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. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:432
`.wc-console #wc-upload-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. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:449
`.progress-bar-animated` moves (`animation: progress-bar-stripes 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5056
`.icon.pulse` moves (`animation-name: pulse-animation`) 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. — JFKFiles/frontend/src/pages/search-page/components/page-bar/view-mode-toggler.style.scss:10
`.drawer-dock .drawer-paper-desktop` moves (`transition: width 0.15s 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. — JFKFiles/frontend/src/pages/search-page/components/drawer/drawer.style.scss:22
`.chevron` moves (`transition: transform 0.25s 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. — JFKFiles/frontend/src/common/components/chevron/chevron.style.scss:7
`.sk-circle .sk-child:before` moves (`animation: sk-circleBounceDelay 1.2s infinite ease-in-out both`) 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. — BuildAnIntelligentBot/src/ChatBot/wwwroot/styles/app.css:135
`.wc-message-groups` moves (`transition: transform 0.2s cubic-bezier(0, 0, 0.5, 1)`) 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. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:55
`.wc-suggested-actions` moves (`transition: height 0.2s cubic-bezier(0, 0, 0.5, 1)`) 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. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:70
`.wc-animate-scroll` moves (`transition: left .8s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:495
`.wc-animate-scroll-rapid` moves (`transition: left .4s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:500
`.wc-animate-scroll-near` moves (`transition: left .3s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:505

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.

Do you agree with this assessment?

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 a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 107 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 toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

AX10 · Code composition9.7 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

AX2 · Stateful singletons5.3 / 10Adequate✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

`KinectCaptureProvidersFactory` is a singleton (one shared instance) but mutates instance state outside any lock (currentCaptureProviders; e.g. `currentCaptureProviders` at line 29). — VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:8
`PowerPointGraphicsCaptureItemsFactory` is a singleton (one shared instance) but mutates instance state outside any lock (currentCaptureItems; e.g. `currentCaptureItems` at line 32). — VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:13

What to do

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

Do you agree with this assessment?

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

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

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

The namespaces Sketch2Code.Core.BoxGeometry ↔ Sketch2Code.Core.Entities depend on each other. The lightest dependency in the cycle is Sketch2Code.Core.Entities → Sketch2Code.Core.BoxGeometry (Sketch2Code.Core.Entities.PredictionDetail → Sketch2Code.Core.BoxGeometry.GroupBox, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Sketch2Code/Sketch2Code.Core/Entities/PredictionDetail.cs:2
The namespaces SnipInsight ↔ SnipInsight.Views depend on each other. The lightest dependency in the cycle is SnipInsight.Views → SnipInsight (SnipInsight.Views.MainWindow → SnipInsight.AppManager, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Snip-Insights/SnipInsight/Views/MainWindow.xaml.cs:20
The namespaces Speaker.Recorder.Models ↔ Speaker.Recorder.Services depend on each other. The lightest dependency in the cycle is Speaker.Recorder.Models → Speaker.Recorder.Services (Speaker.Recorder.Models.RecordingSession → Speaker.Recorder.Services.KinectRecorderService, 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. — VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/RecordingSession.cs:2

What to do

Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX6 · Interface segregation10.0 / 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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

C1 · Data Protection6.5 / 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.

Do you agree with this assessment?

C2 · Access Controls0.0 / 10Critical✓ Tool-verified

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

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

No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
`BotController.PostAsync` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — BuildAnIntelligentBot/src/ChatBot/Controllers/BotController.cs:25
`AppController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:30
`AppController.Step2` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:35
`AppController.Step2FromSample` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:78
`AppController.Step3` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:109
`AppController.Upload` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:119
`AppController.callBackEnd` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:146
`AppController.Step4` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:188
`AppController.Step5` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:196
`AppController.TakeSnapshot` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:207
`AppController.Details` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:211
`AppController.File` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:226
`AppController.Loader1` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:232
`AppController.Loader2` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:236
`AppController.SaveFile` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:243
`ErrorController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/ErrorController.cs:11
`LayoutController.Details` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:24
`LayoutController.GroupBox` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:31
`LayoutController.Result` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:38
`LayoutController.RawGroupBox` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:47
`TemplateController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:25
`TemplateController.Uploader` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:35, Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:44
`TemplateController.Prueba` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:39
`TemplateController.Details` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:83
`TemplateController.File` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:96
`TemplateController.FileJson` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:101

What to do

Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code9.8 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×9) — Snip-Insights/SnipInsight/AIServices/AIComponents/OCRControl.xaml.cs:58, Snip-Insights/SnipInsight/Util/FormatStringConverter.cs:23, Snip-Insights/SnipInsight/Util/NullToVisibilityConverter.cs:19, …
A placeholder string ("youremail@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:526

What to do

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs6.9 / 10Adequate✓ Tool-verified

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

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

`CreateSynonyms` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:134
`Index` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:30
`Step3` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:108
`TakeSnapshot` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:207
`Loader1` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:232
`Loader2` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:236
`DeleteAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Snip-Insights/SnipInsight/AppManager.cs:917
`SubmitButtonClickEvent` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:42
`SubmitApiCallEvent` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:47
`SubmitStateTransitionEvent` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:52
`GetContent` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — Snip-Insights/SnipInsight/Views/ControlTreeEnumerator.cs:51
`SettingsPanel.xaml` wires an event to `ScreenCaptureKeyCombo_KeyComboChanged`, whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — Snip-Insights/SnipInsight/Views/SettingsPanel.xaml.cs:94
A placeholder value ("John Doe") is still in shipped code — sample/mock data that was never replaced with the real thing. — REDACTED:323
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×26) — GoogleAssistantConnector/DemoBot/BotUsingCards/Program.cs:27, GoogleAssistantConnector/DemoBot/BotUsingCards/Program.cs:28, GoogleAssistantConnector/DemoBot/BotUsingCards/Startup.cs:104, …
A placeholder e-mail address ("youremail@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:526

What to do

Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.

Do you agree with this assessment?

M1 · Documentation (README)6.3 / 10Adequate✓ Tool-verified

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

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 11 of 13 project(s) that lack one — worth up to 1.7 pts.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure4.0 / 10Weak✓ Tool-verified

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

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

Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
Only 5/13 projects share a common root namespace — the code's module identity is inconsistent.

What to do

Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.

Do you agree with this assessment?

M4 · Documentation accuracy9.7 / 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.

JFKFiles/README.md documents the environment variable `MSDEPLOY_RENAME_LOCKED_FILES`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — JFKFiles/README.md:302
GoogleAssistantConnector/docs/googleAssistantProxy.settings.es.md links to `otherSettings.md`, but `GoogleAssistantConnector/docs/otherSettings.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GoogleAssistantConnector/docs/googleAssistantProxy.settings.es.md:2
GoogleAssistantConnector/DemoBot/BotUsingCards/README.md links to `../../../Installing_CLI_tools.md`, but `Installing_CLI_tools.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — GoogleAssistantConnector/DemoBot/BotUsingCards/README.md:36
Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/docs/_includes/popper-documentation.md`, but `docs/_includes/popper-documentation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sketch2Code/Sketch2Code.Web/Scripts/README.md:56
Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/docs/_includes/tooltip-documentation.md`, but `docs/_includes/tooltip-documentation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sketch2Code/Sketch2Code.Web/Scripts/README.md:68
Sketch2Code/Sketch2Code.Web/Scripts/README.md installs `popper.js` (`npm install popper.js --save`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sketch2Code/Sketch2Code.Web/Scripts/README.md:76
Sketch2Code/Sketch2Code.Web/Scripts/README.md installs `tooltip.js` (`npm install tooltip.js --save`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sketch2Code/Sketch2Code.Web/Scripts/README.md:87
Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `docs/_includes/popper-documentation.md#modifiers--object`, but `Sketch2Code/Sketch2Code.Web/Scripts/docs/_includes/popper-documentation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sketch2Code/Sketch2Code.Web/Scripts/README.md:147
Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/MENTIONS.md`, but `MENTIONS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sketch2Code/Sketch2Code.Web/Scripts/README.md:159
Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `LICENSE.md`, but `Sketch2Code/Sketch2Code.Web/Scripts/LICENSE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Sketch2Code/Sketch2Code.Web/Scripts/README.md:219

What to do

Reconcile the README with reality: JFKFiles/README.md documents the environment variable `MSDEPLOY_RENAME_LOCKED_FILES`, but no code, script or configuration file names it; GoogleAssistantConnector/docs/googleAssistantProxy.settings.es.md links to `otherSettings.md`, but `GoogleAssistantConnector/docs/otherSettings.md` does not exist; GoogleAssistantConnector/DemoBot/BotUsingCards/README.md links to `../../../Installing_CLI_tools.md`, but `Installing_CLI_tools.md` does not exist; Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/docs/_includes/popper-documentation.md`, but `docs/_includes/popper-documentation.md` does not exist; Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/docs/_includes/tooltip-documentation.md`, but `docs/_includes/tooltip-documentation.md` does not exist.

Do you agree with this assessment?

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.

Do you agree with this assessment?

P2 · Observability6.0 / 10Adequate✓ Tool-verified

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

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

Only 6/9 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 9, 5 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
`Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs` reports through `Console.Write…` at line 58 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs:58

What to do

Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

Do you agree with this assessment?

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.

Do you agree with this assessment?

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

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

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

What to do

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

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

Do you agree with this assessment?

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×12) — BuildAnIntelligentBot/src/ChatBot/Services/AzureAuthenticationService.cs:69, BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:16, BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:29, …

What to do

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

Do you agree with this assessment?

PF3 · Async & latency hygiene8.5 / 10Strong✓ Tool-verified

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

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

1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`captureEvent.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs:181

What to do

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

Do you agree with this assessment?

R1 · Type Safety8.5 / 10Strong✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication8.8 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:113 · JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-preview.component.tsx:149 — the two spans are one implementation copied and then locally edited — 210 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:113
JFKFiles/frontend/src/az-api/api.ts:13 · JFKFiles/frontend/src/graph-api/api.ts:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — JFKFiles/frontend/src/az-api/api.ts:13
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:22 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:70 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:22
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:75 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76
JFKFiles/frontend/src/pages/search-page/components/selection-controls/checkbox-list.component.tsx:11 · JFKFiles/frontend/src/pages/search-page/components/selection-controls/year-picker.component.tsx:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — JFKFiles/frontend/src/pages/search-page/components/selection-controls/checkbox-list.component.tsx:11
JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:66 · JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-preview.component.tsx:91 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:66
JFKFiles/frontend/src/common/components/logo-jfk/svg.component.tsx:5 · JFKFiles/frontend/src/common/components/logo-microsoft/svg.component.tsx:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — JFKFiles/frontend/src/common/components/logo-jfk/svg.component.tsx:5
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:32 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:47 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:32
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:52 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:52
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:75 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/SuggestedActionsMapper.js:31 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76
JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-docnode.component.tsx:70 · JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-node.component.tsx:79 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-docnode.component.tsx:70
JFKFiles/frontend/src/pages/search-page/service/service.ts:12 · JFKFiles/frontend/src/pages/search-page/service/service.ts:27 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — JFKFiles/frontend/src/pages/search-page/service/service.ts:12
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/InstructionBuilder.js:83 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/InstructionBuilder.js:103 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/InstructionBuilder.js:83
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:11 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/ListCardMapper.js:2 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:11
JFKFiles/frontend/src/az-api/response.parser.ts:29 · JFKFiles/frontend/src/graph-api/response.parser.ts:27 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — JFKFiles/frontend/src/az-api/response.parser.ts:29
GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/Trace.js:23 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/Trace.js:35 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/Trace.js:23
JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts:168 · JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts:180 — 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. — JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts:168

What to do

Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.

Do you agree with this assessment?

R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

(anonymous) has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:20
(anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — JFKFiles/frontend/src/az-api/payload/payload.parser.ts:16
_buildCarouselCard has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:26
_buildBasicCard has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:27
_buildBasicCard has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:75

Do you agree with this assessment?

R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

Do you agree with this assessment?

R4 · Test Coverage0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

0% of 113 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R5 · Dependency Freshness9.9 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

What to do

Bump outdated dependencies to current versions to limit upgrade debt.

Do you agree with this assessment?

R6 · Tooling0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.

Do you agree with this assessment?

R7 · Dead Code9.7 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

4 file(s) (~3439 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
Unreachable from the 4 application, 4 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (4 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/conversationQueue.js, JFKFiles/frontend/server/index.js, JFKFiles/frontend/src/common/components/pagination/index.ts
Nothing ultimately consumes this binding: its only referrer is the re-export in JFKFiles/frontend/src/graph-api/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in JFKFiles/frontend/src/graph-api/index.ts in the same commit, or the barrel will import a name that no longer exists. — JFKFiles/frontend/src/graph-api/payload.model.ts:10
Nothing ultimately consumes this binding: its only referrer is the re-export in JFKFiles/frontend/src/util/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in JFKFiles/frontend/src/util/index.ts in the same commit, or the barrel will import a name that no longer exists. — JFKFiles/frontend/src/util/log-debug.helper.ts:1
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×2) — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/ListCardMapper.js:4, JFKFiles/frontend/src/pages/search-page/components/page-bar/page-bar.component.tsx:12
Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — JFKFiles/frontend/src/pages/search-page/search-page.container.tsx:170

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene8.0 / 10Strong✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

Imported but not declared in any reachable package.json — installs work only by hoisting accident. — JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx:2

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports3.6 / 10Weak✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

JFKFiles/frontend/src/az-api/payload/filter.parser.ts → JFKFiles/frontend/src/az-api/payload/index.ts → JFKFiles/frontend/src/az-api/payload/filter.parser.ts (one verified cycle inside a mutually-dependent group of 3 files) — JFKFiles/frontend/src/az-api/payload/filter.parser.ts:3
JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx → JFKFiles/frontend/src/pages/detail-page/detail-page.memento.ts → JFKFiles/frontend/src/pages/detail-page/index.ts → JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx (one verified cycle inside a mutually-dependent group of 7 files) — JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx:7
JFKFiles/frontend/src/pages/search-page/service/index.ts → JFKFiles/frontend/src/pages/search-page/service/service.model.ts → JFKFiles/frontend/src/pages/search-page/view-model/index.ts → JFKFiles/frontend/src/pages/search-page/view-model/state.model.ts → JFKFiles/frontend/src/pages/search-page/service/index.ts (one verified cycle inside a mutually-dependent group of 9 files) — JFKFiles/frontend/src/pages/search-page/service/index.ts:2

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

Do you agree with this assessment?

S1 · Web-Security Posture2.0 / 10Critical✓ Tool-verified

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

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

`SAditionalEntropy` is the DPAPI additional entropy and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — Snip-Insights/SnipInsight/Util/RegistrySettings.cs:13
`https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 16 such include(s) across the repository's markup. — Sketch2Code/Sketch2Code.Web/Maqueta/CarrouselTest.html:10
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. (×2) — BuildAnIntelligentBot/src/ChatBot/Program.cs:14, GoogleAssistantConnector/DemoBot/BotUsingCards/Program.cs:18

What to do

Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.

Do you agree with this assessment?

X1 · Async correctness5.3 / 10Adequate✓ Tool-verified

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

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

`StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin. (×4) — Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs:90, JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:110, JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:150, …
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×2) — Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:62, Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:101
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×11) — VirtualStage/Speaker.Recorder/Speaker.Recorder/App.xaml.cs:24, VirtualStage/Speaker.Recorder/Speaker.Recorder/App.xaml.cs:94, VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs:73, …
`Task.WaitAny` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAny(…)` instead. — BuildAnIntelligentBot/src/ChatBot/Services/TranslatorSpeechService.cs:81
`Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method. — JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:251

What to do

Blocking `StreamReader.ReadToEnd` inside an `async` method

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X18 · Disposal-pattern correctness5.5 / 10Adequate✓ Tool-verified

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

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

`myProcess` is a `Process`, which implements `IDisposable`, and it is created here (line 651). Every use of it in `CreateAndOpenICSFile` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var myProcess = …;`), which releases it at the end of the scope on every path including a throw. — Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:651
`OneNoteManager` declares a finalizer (line 62), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — REDACTED:62
`TrayIcon` declares a finalizer (line 45), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Snip-Insights/SnipInsight/TrayIcon.cs:45
`t` is a `Timer`, which implements `IDisposable`, and it is created here (line 46). Every use of it in `Control_Loaded` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var t = …;`), which releases it at the end of the scope on every path including a throw. — Snip-Insights/SnipInsight/Views/ToastControl.xaml.cs:46
`AppManager` declares a finalizer (line 310), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Snip-Insights/SnipInsight/AppManager.cs:310
`ImageCaptureManager` declares a finalizer (line 48), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Snip-Insights/SnipInsight/ImageCapture/ImageCaptureManager.cs:48
`SnipInsightLink` declares a finalizer (line 19), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Snip-Insights/SnipInsight/Package/SnipInsightLink.cs:19

What to do

Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X2 · Cancellation propagation4.5 / 10Weak✓ Tool-verified

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

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

Only 12/120 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) — Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs:38, Snip-Insights/SnipInsight/AIServices/AILogic/ImageSearchHandler.cs:53, Snip-Insights/SnipInsight/AIServices/AILogic/NewsHandler.cs:30, …

What to do

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

Do you agree with this assessment?

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

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

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

The guard on line 23 rejects `destinationTypeFullName` and line 25 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(destinationTypeFullName)` is true of a value that is NOT null: it is satisfied by an EMPTY `destinationTypeFullName`, and on that path `destinationTypeFullName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — VirtualStage/Speaker.Recorder/Speaker.Recorder/Helpers/TypeConverterHelper.cs:25
The guard on line 21 rejects `destinationTypeFullName` and line 23 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(destinationTypeFullName)` is true of a value that is NOT null: it is satisfied by an EMPTY `destinationTypeFullName`, and on that path `destinationTypeFullName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/Controls/TypeConverterHelper.cs:23
The guard on line 262 rejects `folderId` and line 263 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(folderId)` is true of a value that is NOT null: it is satisfied by an EMPTY `folderId`, and on that path `folderId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs:263
The guard on line 40 rejects `projectName` and line 40 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(projectName)` is true of a value that is NOT null: it is satisfied by an EMPTY `projectName`, and on that path `projectName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Sketch2Code/Sketch2Code.AI/CustomVisionClient.cs:40
The guard on line 61 rejects `projectName` and line 61 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(projectName)` is true of a value that is NOT null: it is satisfied by an EMPTY `projectName`, and on that path `projectName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Sketch2Code/Sketch2Code.AI/CustomVisionClient.cs:61
The guard on line 15 rejects `name` and line 16 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — Sketch2Code/Sketch2Code.Web/Models/PredictionViewModel.cs:16
The guard on line 23 rejects `speechKey` and line 25 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(speechKey)` is true of a value that is NOT null: it is satisfied by an EMPTY `speechKey`, and on that path `speechKey` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — BuildAnIntelligentBot/src/ChatBot/Middlewares/TranslatorSpeechMiddleware.cs:25
The guard on line 28 rejects `translatorKey` and line 30 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(translatorKey)` is true of a value that is NOT null: it is satisfied by an EMPTY `translatorKey`, and on that path `translatorKey` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — BuildAnIntelligentBot/src/ChatBot/Middlewares/TranslatorSpeechMiddleware.cs:30
The guard on line 18 rejects `key` and line 20 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(key)` is true of a value that is NOT null: it is satisfied by an EMPTY `key`, and on that path `key` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — BuildAnIntelligentBot/src/ChatBot/Models/AzureAuthToken.cs:20

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped3.1 / 10Weak✓ Tool-verified

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

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

`Model.Html` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:16
`__html` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:56
`wrap[1]+elem.replace(rxhtmlTag,"<$1></$2>")+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0-vsdoc.js:1130
`value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0-vsdoc.js:4234, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5862, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:5862
`expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1236, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1237, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:1236, …
`wrap[1]+jQuery.htmlPrefilter(elem)+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4677, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4677
`style` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — Sketch2Code/Sketch2Code.Web/Scripts/modernizr-2.6.2.js:148
`cssText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — Sketch2Code/Sketch2Code.Web/Scripts/modernizr-2.6.2.js:1094

What to do

Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

`throw e;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. — Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs:60
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×19) — Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:337, Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:359, REDACTED:285, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:92, Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:73, Snip-Insights/SnipInsight/Util/DpiUtilities.cs:45

What to do

Rethrow loses stack trace (`throw ex;`)

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X4 · Structured logging2.0 / 10Critical✓ Tool-verified

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

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

Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×40) — VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:25, VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:28, VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:45, …

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

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 `rect`: line 241 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 242 then dereferences it directly as `rect.Stroke` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:242
This method contradicts itself about `rect`: line 356 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 358 then dereferences it directly as `rect.Tag` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:358
This method contradicts itself about `par`: line 360 assigns it with `as Canvas`, which hands back null rather than throwing when the value is not a `Canvas`, but line 361 then dereferences it directly as `par.Children` 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 `par` once before the first use and handle the null case, or cast with `(Canvas)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:361
This method contradicts itself about `otherRect`: line 363 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 364 then dereferences it directly as `otherRect.Stroke` 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 `otherRect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:364
This method contradicts itself about `rect`: line 375 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 377 then dereferences it directly as `rect.Tag` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:377
This method contradicts itself about `rect`: line 390 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 391 then dereferences it directly as `rect.Tag` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:391
This method contradicts itself about `view`: line 68 assigns it with `as ListCollectionView`, which hands back null rather than throwing when the value is not a `ListCollectionView`, but line 71 then dereferences it directly as `view.CustomSort` 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 `view` once before the first use and handle the null case, or cast with `(ListCollectionView)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Snip-Insights/SnipInsight/Views/LibraryPanel.xaml.cs:71
This method contradicts itself about `item`: line 75 writes `item?.ProviderKey`, which says `item` can be null, but line 71 then dereferences it directly as `item.Stop` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `item` truly cannot be null here, the `?.` is misleading. Settle it one way — test `item` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/RecordingSession.cs:71
This method contradicts itself about `img`: line 32 assigns it with `as Bitmap`, which hands back null rather than throwing when the value is not a `Bitmap`, but line 34 then dereferences it directly as `img.Clone` 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 `img` once before the first use and handle the null case, or cast with `(Bitmap)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Sketch2Code/Sketch2Code.Core/Helpers/ImageHelper.cs:34
0/1 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 `!`.

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

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

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC4 · Keyboard semantics	2.1.1, 2.4.3	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement 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.

Lens	Score	Rating	Impact
Code Health	42%	Weak — gated by D18, X4, X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	72%	Adequate — gated by R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	53%	Adequate — gated by D34	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	16%	Critical — gated by R4, R6, P1, P3, P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	27%	Weak — gated by D29, D30, D31, D44, C2, S1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	39%	Weak — gated by AC4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	85%	Strong	Strongest area.

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

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

SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

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

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

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

Not included — 27 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.

AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D11 Test Reliability — Test reliability not measured — no test run produced results
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — Not assessed, and this one is on us: 1 of the 1 handler(s) found here write to persistent state through an entry point this check does not yet recognise (an explicitly-implemented interface method, or a static handler method). Idempotency was neither confirmed nor ruled out for them — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — no CI workflow found
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 128 finding(s)

D17 · Explicit Debt · WriteOnlyPrivateField · ×26

WriteOnlyPrivateField BuildAnIntelligentBot/src/ChatBot/Dialogs/ReservationDialog.cs:24 — private TextToSpeechService _ttsService — 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 BuildAnIntelligentBot/src/ChatBot/EchoBot.cs:31 — private EchoBotAccessors _accessors — 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 BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:16 — private HttpClient Client — 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 BuildAnIntelligentBot/src/ChatBot/Startup.cs:32 — private ILoggerFactory _loggerFactory — 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 BuildAnIntelligentBot/src/ChatBot/Startup.cs:33 — private bool _isProduction — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs:25 — private string detectedLanguage — 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 Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageSearchViewModel.cs:51 — private double wrapPanelDefinedWidth — 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 Snip-Insights/SnipInsight/AIServices/AIViewModels/ProductSearchViewModel.cs:54 — private double wrapPanelDefinedWidth — 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 Snip-Insights/SnipInsight/AppManager.cs:1853 — private Visibility _mainWindowVisibilityBeforeCapture — 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 Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:17 — private ContentPresenter contentArea — 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:394 — private string SectionNodeXPath — 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:395 — private string PageNodeXPath — 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 Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:14 — private string versionNumber — 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 Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:14 — private string macAddress — 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 Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:182 — private string _langName — 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 Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:184 — private string _sessionId — 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 Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:189 — private string _appName — 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 Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:190 — private string _appVersion — 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 Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:191 — private string _os — 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 Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:192 — private string _process — 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 Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:193 — private bool _itInstall — 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 VirtualStage/Speaker.Recorder/Speaker.Recorder/Capture/Direct3D11Helper.cs:9 — private Guid IInspectable — 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 VirtualStage/Speaker.Recorder/Speaker.Recorder/Capture/Direct3D11Helper.cs:10 — private Guid ID3D11Resource — 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 VirtualStage/Speaker.Recorder/Speaker.Recorder/Capture/Direct3D11Helper.cs:11 — private Guid IDXGIAdapter3 — 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 VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs:40 — private string playbackPath — 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.
+ 1 more in this group — see findings.md.

AC1 · Text alternatives · <img> without a text alternative · ×20

<img> without a text alternative Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:78 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:94 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:105 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:116 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Maqueta/Details.html:127 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Maqueta/Index.html:94 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Maqueta/IndexCarrousel.html:179 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/App/Index.cshtml:94 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:19 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:21 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative REDACTED:30 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative REDACTED:32 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative REDACTED:46 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/Template/Prueba.cshtml:40 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/Template/Prueba1.cshtml:4 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/Template/Prueba3.cshtml:15 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/Template/Prueba3.cshtml:21 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/Template/Prueba3.cshtml:24 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/Template/Prueba3.cshtml:27 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative Sketch2Code/Sketch2Code.Web/Views/Template/Prueba3.cshtml:30 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.

D17 · Explicit Debt · EmptyCatchBlock · ×19

EmptyCatchBlock BuildAnIntelligentBot/src/ChatBot/Services/TextToSpeechService.cs:32 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:337 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:359 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/AppManager.cs:215 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:285 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:25 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/Diagnostics.cs:58 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/Diagnostics.cs:78 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/Diagnostics.cs:102 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:793 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:817 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:837 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:861 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:881 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Snip-Insights/SnipInsight/Util/RegistrySettings.cs:905 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs:146 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:58 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/IdentificationService/DesktopNameIdentificationService.cs:39 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/IdentificationService/DesktopNameIdentificationService.cs:52 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.

D30 · Dependency Vulnerabilities · High CVE · ×15

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

AC2 · Forms & labels · <select> without a programmatic label · ×6

<select> without a programmatic label Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1237 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1276 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4594 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:1237 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:1276 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4594 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

AC2 · Forms & labels · <input> without a programmatic label · ×4

<input> without a programmatic label JFKFiles/frontend/src/pages/home-page/components/search/search-input.component.tsx:25 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2710 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:2710 — 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 Sketch2Code/Sketch2Code.Web/Views/Template/Uploader.cshtml:22 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

AC2 · Forms & labels · Link with no accessible name · ×4

Link with no accessible name Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1275 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2697 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:1275 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:2697 — 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.

AC3 · Page structure · <html> without a lang · ×4

<html> without a lang BuildAnIntelligentBot/src/ChatBot/wwwroot/default.htm:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang JFKFiles/frontend/src/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:7 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang Sketch2Code/Sketch2Code.Web/Views/Shared/_FlatLayout.cshtml:8 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").

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

Namespace dependency cycle Sketch2Code/Sketch2Code.Core/Entities/PredictionDetail.cs:2 — The namespaces Sketch2Code.Core.BoxGeometry ↔ Sketch2Code.Core.Entities depend on each other. The lightest dependency in the cycle is Sketch2Code.Core.Entities → Sketch2Code.Core.BoxGeometry (Sketch2Code.Core.Entities.PredictionDetail → Sketch2Code.Core.BoxGeometry.GroupBox, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle Snip-Insights/SnipInsight/Views/MainWindow.xaml.cs:20 — The namespaces SnipInsight ↔ SnipInsight.Views depend on each other. The lightest dependency in the cycle is SnipInsight.Views → SnipInsight (SnipInsight.Views.MainWindow → SnipInsight.AppManager, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/RecordingSession.cs:2 — The namespaces Speaker.Recorder.Models ↔ Speaker.Recorder.Services depend on each other. The lightest dependency in the cycle is Speaker.Recorder.Models → Speaker.Recorder.Services (Speaker.Recorder.Models.RecordingSession → Speaker.Recorder.Services.KinectRecorderService, 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.

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

REDACTED
REDACTED
REDACTED

AC2 · Forms & labels · <textarea> without a programmatic label · ×2

<textarea> without a programmatic label Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4758 — 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 Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4758 — 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 · <label> that labels no control · ×2

<label> that labels no control Sketch2Code/Sketch2Code.Web/Views/Shared/_Label.cshtml:2 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control Sketch2Code/Sketch2Code.Web/Views/Template/Index.cshtml:13 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.

AC3 · Page structure · Document without a <title> · ×2

Document without a <title> BuildAnIntelligentBot/src/ChatBot/wwwroot/default.htm:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:7 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.

D17 · Explicit Debt · NoWarnInCsproj · ×2

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

AC4 · Keyboard semantics · Hover-only interaction on <rect> · ×1

Hover-only interaction on <rect> JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-svg.component.tsx:25 — This <rect> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.

AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×1

Click handler on a non-interactive <div> JFKFiles/frontend/src/pages/search-page/components/item/item.component.tsx:52 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.

D17 · Explicit Debt · NoWarnInCsproj repeated 10 times in 2 files · ×1

NoWarnInCsproj repeated 10 times in 2 files VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP/Speaker.Recorder.UWP.csproj:26 — The identical NoWarnInCsproj (`2008`) appears 10 times in 2 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 10 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)

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

REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×1

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

R8 · Dependency Hygiene · Unlisted import 'react-router' · ×1

Unlisted import 'react-router' JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (2 files) · ×1

Import cycle (2 files) JFKFiles/frontend/src/az-api/payload/filter.parser.ts:3 — JFKFiles/frontend/src/az-api/payload/filter.parser.ts → JFKFiles/frontend/src/az-api/payload/index.ts → JFKFiles/frontend/src/az-api/payload/filter.parser.ts (one verified cycle inside a mutually-dependent group of 3 files)

R9 · Circular Imports · Import cycle (3 files) · ×1

Import cycle (3 files) JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx:7 — JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx → JFKFiles/frontend/src/pages/detail-page/detail-page.memento.ts → JFKFiles/frontend/src/pages/detail-page/index.ts → JFKFiles/frontend/src/pages/detail-page/detail-page.container.tsx (one verified cycle inside a mutually-dependent group of 7 files)

R9 · Circular Imports · Import cycle (4 files) · ×1

Import cycle (4 files) JFKFiles/frontend/src/pages/search-page/service/index.ts:2 — JFKFiles/frontend/src/pages/search-page/service/index.ts → JFKFiles/frontend/src/pages/search-page/service/service.model.ts → JFKFiles/frontend/src/pages/search-page/view-model/index.ts → JFKFiles/frontend/src/pages/search-page/view-model/state.model.ts → JFKFiles/frontend/src/pages/search-page/service/index.ts (one verified cycle inside a mutually-dependent group of 9 files)

S1 · Web-Security Posture · Cryptographic key material is a compile-time constant · ×1

Cryptographic key material is a compile-time constant Snip-Insights/SnipInsight/Util/RegistrySettings.cs:13 — `SAditionalEntropy` is the DPAPI additional entropy and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.

Serious — 532 finding(s)

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 27 more in this group — see findings.md.

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

Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs:38 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/ImageSearchHandler.cs:53 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetResult Snip-Insights/SnipInsight/AIServices/AILogic/NewsHandler.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/NewsHandler.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetResult Snip-Insights/SnipInsight/AIServices/AILogic/LUISInsights.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/LUISInsights.cs:54 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/ProductSearchHandler.cs:50 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetCelebrities Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:170 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetLandmarks Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:256 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadAnalysis Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:335 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadImages Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageSearchViewModel.cs:98 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadText Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetLUISInsights Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:435 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadProducts Snip-Insights/SnipInsight/AIServices/AIViewModels/ProductSearchViewModel.cs:101 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetResult Snip-Insights/SnipInsight/AIServices/CloudService.cs:79 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/CloudService.cs:100 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RequestAndRetry Snip-Insights/SnipInsight/AIServices/CloudService.cs:123 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetResult Snip-Insights/SnipInsight/AIServices/AILogic/EntitySearchHandler.cs:34 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Run Snip-Insights/SnipInsight/AIServices/AILogic/EntitySearchHandler.cs:58 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Send Snip-Insights/SnipInsight/Util/LogUploader.cs:113 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteButton_OnLeftMouseDown Snip-Insights/SnipInsight/Views/LibraryPanel.xaml.cs:136 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleDelete Snip-Insights/SnipInsight/Views/LibraryPanel.xaml.cs:163 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: HandleDelete Snip-Insights/SnipInsight/Views/LibraryPanel.xaml.cs:171 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowLibraryPanel Snip-Insights/SnipInsight/AppManager.cs:657 — No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartLoadingSnipInsights Snip-Insights/SnipInsight/AppManager.cs:698 — No CancellationToken parameter — this work can't be stopped early once started.
+ 14 more in this group — see findings.md.

C2 · Access Controls · No authorization · ×28

No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization BuildAnIntelligentBot/src/ChatBot/Controllers/BotController.cs:25 — `BotController.PostAsync` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:30 — `AppController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:35 — `AppController.Step2` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:78 — `AppController.Step2FromSample` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:109 — `AppController.Step3` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:119 — `AppController.Upload` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:146 — `AppController.callBackEnd` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:188 — `AppController.Step4` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:196 — `AppController.Step5` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:207 — `AppController.TakeSnapshot` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:211 — `AppController.Details` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:226 — `AppController.File` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:232 — `AppController.Loader1` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:236 — `AppController.Loader2` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:243 — `AppController.SaveFile` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/ErrorController.cs:11 — `ErrorController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:24 — `LayoutController.Details` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:31 — `LayoutController.GroupBox` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:38 — `LayoutController.Result` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/LayoutController.cs:47 — `LayoutController.RawGroupBox` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:25 — `TemplateController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:35 — `TemplateController.Uploader` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:39 — `TemplateController.Prueba` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:44 — `TemplateController.Uploader` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
+ 3 more in this group — see findings.md.

D17 · Explicit Debt · TodoComment · ×22

TodoComment Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:170 — //TODO: Skip this once we generate online slices — 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.
TodoComment Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:175 — //TODO: Store this as Text — 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.
TodoComment Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:182 — //TODO: Store this as Text — 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.
TodoComment Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs:70 — //TODO: After Refactoring Log results status and api run time — 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.
TodoComment Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:655 — // TODO: monitor process of exit code (for telemetry) — 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.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:678 — // TODO: Make a shortcut for this panel — 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.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1145 — //TODO: Delete packages — 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.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1304 — //TODO: Delete package — 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.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1633 — // TODO: Fix the attachment name — 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.
TodoComment Snip-Insights/SnipInsight/AppManager.cs:1687 — // TODO: Check which OneNote function is used — 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.
TodoComment Snip-Insights/SnipInsight/ImageCapture/SmartBoundaryDetection.cs:201 — //TODO(qiazhang) should we return the smallest window? — 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.
TodoComment Snip-Insights/SnipInsight/Ink/AcetateLayerInkCanvas.cs:21 — // TODO: Fix Ink Cursor — 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.
TodoComment Snip-Insights/SnipInsight/Package/SnipInsightLink.cs:98 — //TODO: Need to add to resoure since date format can be different in other countries. — 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.
TodoComment Snip-Insights/SnipInsight/Package/SnipInsightLink.cs:110 — // TODO: Need to add to resource. — 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.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:39 — // TODO: Log generic user events — 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.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:44 — // TODO : Log clicks on UI elements by users — 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.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:49 — // TODO : Log web request to AI services — 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.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:57 — // TODO : Log transition of states in application. — 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.
TodoComment Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:65 — //TODO: Initialize the or set the logging module to be used to gather user telemetry — 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.
TodoComment Snip-Insights/SnipInsight/TrayIcon.cs:20 — // TODO: Update the tray icon — 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.
TodoComment Snip-Insights/SnipInsight/ViewModels/ViewModelLocator.cs:62 — // TODO Clear the ViewModels — 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.
TodoComment Snip-Insights/SnipInsight/Views/ControlTreeEnumerator.cs:55 — // TODO: Can't find a way to get to the children of a UserControl... — 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.

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

Swallowed exception (empty catch) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:337 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:359 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:285 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:25 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/Diagnostics.cs:58 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/Diagnostics.cs:78 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/Diagnostics.cs:102 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/RegistrySettings.cs:793 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/RegistrySettings.cs:817 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/RegistrySettings.cs:837 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/RegistrySettings.cs:861 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/RegistrySettings.cs:881 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/Util/RegistrySettings.cs:905 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) Snip-Insights/SnipInsight/AppManager.cs:215 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs:146 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:58 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/IdentificationService/DesktopNameIdentificationService.cs:39 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/IdentificationService/DesktopNameIdentificationService.cs:52 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) BuildAnIntelligentBot/src/ChatBot/Services/TextToSpeechService.cs:32 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.

D29 · Static Analysis (SAST) · REDACTED

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

AC3 · Page structure · Page without a main landmark · ×16

Page without a main landmark BuildAnIntelligentBot/src/ChatBot/wwwroot/default.htm:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark GoogleAssistantConnector/DemoBot/BotUsingCards/wwwroot/default.htm:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark JFKFiles/frontend/src/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Sketch2Code/Sketch2Code.Web/Maqueta/CarrouselTest.html: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 Sketch2Code/Sketch2Code.Web/Maqueta/Details.html: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 Sketch2Code/Sketch2Code.Web/Maqueta/Index.html: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 Sketch2Code/Sketch2Code.Web/Maqueta/IndexCarrousel.html: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 Sketch2Code/Sketch2Code.Web/Maqueta/Step2.html: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 Sketch2Code/Sketch2Code.Web/Maqueta/Step3.html: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 Sketch2Code/Sketch2Code.Web/Maqueta/Step4.html: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 Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:7 — 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 Sketch2Code/Sketch2Code.Web/Views/Shared/_DebugLayout.cshtml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Sketch2Code/Sketch2Code.Web/Views/Shared/_FlatLayout.cshtml:8 — 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 Sketch2Code/Sketch2Code.Web/Views/Shared/_Layout.cshtml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Sketch2Code/Sketch2Code.Web/Views/Shared/_LayoutDetails.cshtml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Sketch2Code/Sketch2Code.Web/Views/Shared/_main.cshtml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.

D17 · Explicit Debt · CommentedOutCode · ×14

CommentedOutCode Sketch2Code/Sketch2Code.Web/Controllers/ErrorController.cs:15 — 5 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Views/EditorSideNavigation.xaml.cs:132 — 5 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Views/SettingsPanel.xaml.cs:153 — 5 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Controls/Ariadne/AriMenuItemBase.cs:55 — 8 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:156 — 4 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/ImageCapture/ScreenshotImage.cs:47 — 4 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Ink/AcetateLayerInkCanvas.cs:22 — 4 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Views/SettingsPanel.xaml.cs:41 — 4 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:217 — 4 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/ImageCapture/ScreenProperties.cs:71 — 3 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Views/SettingsPanel.xaml.cs:166 — 3 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:239 — 3 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:346 — 3 consecutive commented-code lines
CommentedOutCode Snip-Insights/SnipInsight/ImageCapture/SmartBoundaryDetection.cs:80 — 6 consecutive commented-code lines

X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×14

Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Views/App/Step5_old.cshtml:16 — `Model.Html` is text this program did not author, and it is written into the text of an element through Razor's `Html.Raw` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:56 — `__html` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0-vsdoc.js:1130 — `wrap[1]+elem.replace(rxhtmlTag,"<$1></$2>")+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0-vsdoc.js:4234 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1236 — `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1237 — `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4677 — `wrap[1]+jQuery.htmlPrefilter(elem)+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5862 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:1236 — `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:1237 — `expando` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4677 — `wrap[1]+jQuery.htmlPrefilter(elem)+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:5862 — `value` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/modernizr-2.6.2.js:148 — `style` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped Sketch2Code/Sketch2Code.Web/Scripts/modernizr-2.6.2.js:1094 — `cssText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×12

Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/AzureAuthenticationService.cs:69 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:16 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:29 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:55 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience BuildAnIntelligentBot/src/ChatBot/Utils/AudioUtils.cs:15 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:31 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:135 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:73 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:46 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience Snip-Insights/SnipInsight/AIServices/CloudService.cs:59 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience Snip-Insights/SnipInsight/Util/LogUploader.cs:135 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/AppUpdaterService.cs:29 — `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).

AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×11

Animation without a prefers-reduced-motion guard GoogleAssistantConnector/DemoBot/BotUsingCards/wwwroot/default.htm:205 — `.ms-logo-container` moves (`transition: bottom 400ms`) 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 Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5056 — `.progress-bar-animated` moves (`animation: progress-bar-stripes 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard JFKFiles/frontend/src/pages/search-page/components/page-bar/view-mode-toggler.style.scss:10 — `.icon.pulse` moves (`animation-name: pulse-animation`) 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 JFKFiles/frontend/src/pages/search-page/components/drawer/drawer.style.scss:22 — `.drawer-dock .drawer-paper-desktop` moves (`transition: width 0.15s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard JFKFiles/frontend/src/common/components/chevron/chevron.style.scss:7 — `.chevron` moves (`transition: transform 0.25s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/styles/app.css:135 — `.sk-circle .sk-child:before` moves (`animation: sk-circleBounceDelay 1.2s infinite ease-in-out both`) 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 BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:55 — `.wc-message-groups` moves (`transition: transform 0.2s cubic-bezier(0, 0, 0.5, 1)`) 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 BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:70 — `.wc-suggested-actions` moves (`transition: height 0.2s cubic-bezier(0, 0, 0.5, 1)`) 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 BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:495 — `.wc-animate-scroll` moves (`transition: left .8s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:500 — `.wc-animate-scroll-rapid` moves (`transition: left .4s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:505 — `.wc-animate-scroll-near` moves (`transition: left .3s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.

AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×11

Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap-reboot.css:156 — `a:not([href]):not([tabindex]):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 Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:186 — `a:not([href]):not([tabindex]):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 Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:2343 — `.btn.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 Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:3727 — `.custom-range: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 Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5316 — `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5370 — `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:5908 — `.carousel-control-prev: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 JFKFiles/frontend/src/pages/home-page/components/search/search-input.style.scss:25 — `.container .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 BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:48 — `.wc-message-groups` 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 BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:432 — `.wc-console input[type=text]` 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 BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:449 — `.wc-console #wc-upload-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.

X1 · Async correctness · async void method · ×11

async void method: OnStartup VirtualStage/Speaker.Recorder/Speaker.Recorder/App.xaml.cs:24 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnExit VirtualStage/Speaker.Recorder/Speaker.Recorder/App.xaml.cs:94 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OpenDevice VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs:73 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: TransferSpeedLoop VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:344 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AcceptStopUploadDialog VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs:84 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: PauseUpload VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs:105 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: PlayUpload VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs:110 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Upload VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/PlayerViewModel.cs:115 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: KinectDeviceCountUpdater VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/RecordViewModel.cs:224 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AceptsEmptyDialog VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/RecordViewModel.cs:266 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SetVideos VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/VideosPlayer.xaml.cs:39 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.

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

Unfinished stub — throws NotImplementedException Snip-Insights/SnipInsight/AIServices/AIComponents/OCRControl.xaml.cs:58 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Snip-Insights/SnipInsight/Util/FormatStringConverter.cs:23 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Snip-Insights/SnipInsight/Util/NullToVisibilityConverter.cs:19 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Snip-Insights/SnipInsight/Util/StringToVisibility.cs:30 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Snip-Insights/SnipInsight/Views/MainWindow.xaml.cs:413 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException Snip-Insights/SnipInsight/Views/TopRibbon.xaml.cs:41 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException VirtualStage/Speaker.Recorder/Speaker.Recorder/Converters/BoolToVisibilityConverter.cs:31 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException VirtualStage/Speaker.Recorder/Speaker.Recorder/Converters/NullToVisibilityConverter.cs:26 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException VirtualStage/Speaker.Recorder/Speaker.Recorder/Converters/PathToFileNameConverter.cs:22 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.

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

Argument guard throws the exception its own condition disproves VirtualStage/Speaker.Recorder/Speaker.Recorder/Helpers/TypeConverterHelper.cs:25 — The guard on line 23 rejects `destinationTypeFullName` and line 25 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(destinationTypeFullName)` is true of a value that is NOT null: it is satisfied by an EMPTY `destinationTypeFullName`, and on that path `destinationTypeFullName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/Controls/TypeConverterHelper.cs:23 — The guard on line 21 rejects `destinationTypeFullName` and line 23 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(destinationTypeFullName)` is true of a value that is NOT null: it is satisfied by an EMPTY `destinationTypeFullName`, and on that path `destinationTypeFullName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs:263 — The guard on line 262 rejects `folderId` and line 263 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(folderId)` is true of a value that is NOT null: it is satisfied by an EMPTY `folderId`, and on that path `folderId` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Sketch2Code/Sketch2Code.AI/CustomVisionClient.cs:40 — The guard on line 40 rejects `projectName` and line 40 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(projectName)` is true of a value that is NOT null: it is satisfied by an EMPTY `projectName`, and on that path `projectName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Sketch2Code/Sketch2Code.AI/CustomVisionClient.cs:61 — The guard on line 61 rejects `projectName` and line 61 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(projectName)` is true of a value that is NOT null: it is satisfied by an EMPTY `projectName`, and on that path `projectName` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves Sketch2Code/Sketch2Code.Web/Models/PredictionViewModel.cs:16 — The guard on line 15 rejects `name` and line 16 reports that rejection as `ArgumentNullException` — but the condition's own test `String.IsNullOrWhiteSpace(name)` is true of a value that is NOT null: it is satisfied by an EMPTY `name`, and on that path `name` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves BuildAnIntelligentBot/src/ChatBot/Middlewares/TranslatorSpeechMiddleware.cs:25 — The guard on line 23 rejects `speechKey` and line 25 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(speechKey)` is true of a value that is NOT null: it is satisfied by an EMPTY `speechKey`, and on that path `speechKey` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves BuildAnIntelligentBot/src/ChatBot/Middlewares/TranslatorSpeechMiddleware.cs:30 — The guard on line 28 rejects `translatorKey` and line 30 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(translatorKey)` is true of a value that is NOT null: it is satisfied by an EMPTY `translatorKey`, and on that path `translatorKey` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves BuildAnIntelligentBot/src/ChatBot/Models/AzureAuthToken.cs:20 — The guard on line 18 rejects `key` and line 20 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(key)` is true of a value that is NOT null: it is satisfied by an EMPTY `key`, and on that path `key` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.

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

Symbol treated as nullable, then dereferenced unguarded Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:242 — This method contradicts itself about `rect`: line 241 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 242 then dereferences it directly as `rect.Stroke` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:358 — This method contradicts itself about `rect`: line 356 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 358 then dereferences it directly as `rect.Tag` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:361 — This method contradicts itself about `par`: line 360 assigns it with `as Canvas`, which hands back null rather than throwing when the value is not a `Canvas`, but line 361 then dereferences it directly as `par.Children` 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 `par` once before the first use and handle the null case, or cast with `(Canvas)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:364 — This method contradicts itself about `otherRect`: line 363 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 364 then dereferences it directly as `otherRect.Stroke` 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 `otherRect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:377 — This method contradicts itself about `rect`: line 375 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 377 then dereferences it directly as `rect.Tag` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:391 — This method contradicts itself about `rect`: line 390 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 391 then dereferences it directly as `rect.Tag` 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 `rect` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded Snip-Insights/SnipInsight/Views/LibraryPanel.xaml.cs:71 — This method contradicts itself about `view`: line 68 assigns it with `as ListCollectionView`, which hands back null rather than throwing when the value is not a `ListCollectionView`, but line 71 then dereferences it directly as `view.CustomSort` 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 `view` once before the first use and handle the null case, or cast with `(ListCollectionView)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/RecordingSession.cs:71 — This method contradicts itself about `item`: line 75 writes `item?.ProviderKey`, which says `item` can be null, but line 71 then dereferences it directly as `item.Stop` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `item` truly cannot be null here, the `?.` is misleading. Settle it one way — test `item` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded Sketch2Code/Sketch2Code.Core/Helpers/ImageHelper.cs:34 — This method contradicts itself about `img`: line 32 assigns it with `as Bitmap`, which hands back null rather than throwing when the value is not a `Bitmap`, but line 34 then dereferences it directly as `img.Clone` 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 `img` once before the first use and handle the null case, or cast with `(Bitmap)` so the failure is reported where it happens — rather than leaving the two readings side by side.

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

Fake-async — async method never awaits JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:134 — `CreateSynonyms` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:30 — `Index` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:108 — `Step3` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:207 — `TakeSnapshot` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:232 — `Loader1` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:236 — `Loader2` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Snip-Insights/SnipInsight/AppManager.cs:917 — `DeleteAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

D30 · Dependency Vulnerabilities · Medium CVE · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D6 · Cohesion (LCOM4) · Low cohesion · ×6

Low cohesion: MainWindow (LCOM4 10) Snip-Insights/SnipInsight/Views/MainWindow.xaml.cs:20 — MainWindow's methods fall into 10 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 10 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: ToolWindow (LCOM4 6) Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:23 — ToolWindow's methods fall into 6 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 6 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: AppManager (LCOM4 5) Snip-Insights/SnipInsight/AppManager.cs:38 — AppManager's methods fall into 5 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 5 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: ImageCaptureWindow (LCOM4 4) Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:21 — ImageCaptureWindow'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: LibraryPanel (LCOM4 4) Snip-Insights/SnipInsight/Views/LibraryPanel.xaml.cs:19 — LibraryPanel'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: MainWindow (LCOM4 4) VirtualStage/Speaker.Recorder/Speaker.Recorder/MainWindow.xaml.cs:17 — MainWindow'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.

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

Duplicated block (7 lines × 2) Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:352 — Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:352-358 | Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:386-392 — 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 `Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:352` 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 (7 lines × 2) Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:134 — Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:134-140 | Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:161-167 — 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 `Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:134` 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 after the matched lines, `Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:141` calls `Permit` and `Snip-Insights/SnipInsight/StateMachine/StateMachine.cs:168` 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 (7 lines × 2) Sketch2Code/Sketch2Code.Web/Helpers/ControllerHelper.cs:17 — Sketch2Code/Sketch2Code.Web/Helpers/ControllerHelper.cs:17-23 | Sketch2Code/Sketch2Code.Web/Helpers/ControllerHelper.cs:30-36 — 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 `Sketch2Code/Sketch2Code.Web/Helpers/ControllerHelper.cs:17` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:39 — Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:39-45 | Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py:37-43 — `Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py` and `Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 43 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) VirtualStage/BackgroundMatting/fixed_threshold.py:34 — VirtualStage/BackgroundMatting/fixed_threshold.py:34-42 | VirtualStage/BackgroundMatting/fixed_threshold.py:44-50 — 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 `VirtualStage/BackgroundMatting/fixed_threshold.py:34` 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.

D44 · Platform End-of-Life · End-of-life runtime · ×5

End-of-life runtime: .NET netcoreapp2.0 Snip-Insights/SnipInsight.Forms.Tests/SnipInsight.Forms.Tests.csproj:3 — Snip-Insights/SnipInsight.Forms.Tests/SnipInsight.Forms.Tests.csproj declares .NET netcoreapp2.0 as this project's target framework, and .NET Core 2.0, support ended 2018-10-01. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2018-10-01 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET netcoreapp2.1 GoogleAssistantConnector/DemoBot/BotUsingCards/CardsBot.csproj:4 — GoogleAssistantConnector/DemoBot/BotUsingCards/CardsBot.csproj declares .NET netcoreapp2.1 as this project's target framework, and .NET Core 2.1, support ended 2021-08-21. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2021-08-21 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.
End-of-life runtime: .NET netcoreapp2.2 BuildAnIntelligentBot/src/ChatBot/ChatBot.csproj:4 — BuildAnIntelligentBot/src/ChatBot/ChatBot.csproj declares .NET netcoreapp2.2 as this project's target framework, and .NET Core 2.2, support ended 2019-12-23. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2019-12-23 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.
End-of-life runtime: .NET netcoreapp3.1 VirtualStage/Speaker.Recorder/Speaker.Recorder/Speaker.Recorder.csproj:4 — VirtualStage/Speaker.Recorder/Speaker.Recorder/Speaker.Recorder.csproj declares .NET netcoreapp3.1 as this project's target framework, and .NET Core 3.1 LTS, support ended 2022-12-13. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-12-13 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.
End-of-life runtime: .NET Framework net461 Sketch2Code/Sketch2Code.Api/Sketch2Code.Api.csproj:3 — Sketch2Code/Sketch2Code.Api/Sketch2Code.Api.csproj declares .NET Framework net461 as this project's target framework, and .NET Framework 4.6.1, support ended 2022-04-26. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-04-26 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.

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

Finalizer on a type that owns no unmanaged resource REDACTED:62 — `OneNoteManager` declares a finalizer (line 62), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource Snip-Insights/SnipInsight/TrayIcon.cs:45 — `TrayIcon` declares a finalizer (line 45), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource Snip-Insights/SnipInsight/AppManager.cs:310 — `AppManager` declares a finalizer (line 310), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource Snip-Insights/SnipInsight/ImageCapture/ImageCaptureManager.cs:48 — `ImageCaptureManager` declares a finalizer (line 48), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource Snip-Insights/SnipInsight/Package/SnipInsightLink.cs:19 — `SnipInsightLink` declares a finalizer (line 19), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.

D3 · God Classes · FileTooLong · ×4

FileTooLong: Scripts/jquery-3.0.0.js Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js — FileTooLong — 4931 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4431 over it, 9.86× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Scripts/jquery-3.0.0.slim.js Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js — FileTooLong — 3871 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3371 over it, 7.74× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SnipInsight/AppManager.cs Snip-Insights/SnipInsight/AppManager.cs — FileTooLong — 1005 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 505 over it, 2.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Util/NativeMethods.cs Snip-Insights/SnipInsight/Util/NativeMethods.cs — FileTooLong — 646 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 146 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

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

Duplicated block (16 lines × 2) VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/Controls/TypeConverterHelper.cs:35 — VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/Controls/TypeConverterHelper.cs:35-50 | VirtualStage/Speaker.Recorder/Speaker.Recorder/Helpers/TypeConverterHelper.cs:37-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/Controls/TypeConverterHelper.cs:35` 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 (16 lines × 2) Snip-Insights/SnipInsight/AIServices/AIModels/ImageSearchModel.cs:49 — Snip-Insights/SnipInsight/AIServices/AIModels/ImageSearchModel.cs:49-64 | Snip-Insights/SnipInsight/AIServices/AIModels/ProductSearchModel.cs:47-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Snip-Insights/SnipInsight/AIServices/AIModels/ImageSearchModel.cs:49` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) REDACTED:40 — REDACTED:40-55 | REDACTED:44-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (16 lines × 2) REDACTED:108 — REDACTED:108-123 | REDACTED:96-111 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 62 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 after the matched lines, `REDACTED:123` calls `grad`, `itemlist` and `REDACTED:111` 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 (10 lines × 2) · ×4

Duplicated block (10 lines × 2) Sketch2Code/Sketch2Code.AI/ObjectDetector.cs:44 — Sketch2Code/Sketch2Code.AI/ObjectDetector.cs:44-53 | Sketch2Code/Sketch2Code.AI/ObjectDetector.cs:72-81 — 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 `Sketch2Code/Sketch2Code.AI/ObjectDetector.cs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) REDACTED:135 — REDACTED:135-144 | REDACTED:40-49 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) REDACTED:196 — REDACTED:196-205 | REDACTED:114-123 — 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 (10 lines × 2) Pix2Story/source/skipthoughts_vectors/training/model.py:61 — Pix2Story/source/skipthoughts_vectors/training/model.py:61-70 | Pix2Story/source/skipthoughts_vectors/training/model.py:138-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

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

Duplicated block (6 lines × 2) Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:200 — Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:200-205 | Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:227-232 — 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 `Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:200` 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 (6 lines × 2) REDACTED:127 — REDACTED:127-132 | Pix2Story/source/skipthoughts_vectors/training/model.py:33-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:127` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) REDACTED:171 — REDACTED:171-176 | REDACTED:80-85 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:78` calls `alloc` and `REDACTED:169` 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.
Duplicated block (6 lines × 2) Pix2Story/source/skipthoughts_vectors/training/model.py:98 — Pix2Story/source/skipthoughts_vectors/training/model.py:98-103 | Pix2Story/source/skipthoughts_vectors/training/model.py:111-116 — 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.

X1 · Async correctness · Blocking `StreamReader.ReadToEnd` inside an `async` method · ×4

Blocking `StreamReader.ReadToEnd` inside an `async` method Snip-Insights/SnipInsight/AIServices/AILogic/TranslationHandler.cs:90 — `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin.
Blocking `StreamReader.ReadToEnd` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:110 — `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin.
Blocking `StreamReader.ReadToEnd` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:150 — `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin.
Blocking `StreamReader.ReadToEnd` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:179 — `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin.

AC3 · Page structure · Heading level jumps from h3 to h5 · ×3

Heading level jumps from h3 to h5 Sketch2Code/Sketch2Code.Web/Maqueta/Index.html:85 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h3 to h5 Sketch2Code/Sketch2Code.Web/Maqueta/IndexCarrousel.html:170 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h3 to h5 Sketch2Code/Sketch2Code.Web/Views/App/Index.cshtml:85 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.

D10 · Test Quality · No assertions · ×3

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

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D3 · God Classes · TooManyMethods · ×3

TooManyMethods: AppManager Snip-Insights/SnipInsight/AppManager.cs — TooManyMethods — 970 significant lines (blank, comment-only and punctuation-only lines excluded), 101 methods. The bar is 30 methods; this is 71 over it, 3.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ToolWindow Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs — TooManyMethods — 298 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AnimationUtilities Snip-Insights/SnipInsight/Util/AnimationUtilities.cs — TooManyMethods — 118 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.

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

Duplicated block (12 lines × 2) Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:121 — Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:121-132 | Snip-Insights/SnipInsight/Util/AppUsageLogger.cs:98-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Snip-Insights/SnipInsight/Util/AppDiagnosticsLogger.cs:121` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) REDACTED:22 — REDACTED:22-33 | REDACTED:23-34 — 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, `REDACTED:34` calls `keys` and `REDACTED:37` 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.
Duplicated block (12 lines × 2) REDACTED:135 — REDACTED:135-146 | Pix2Story/source/skipthoughts_vectors/training/model.py:128-139 — 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.

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

Duplicated block (5 lines × 2) VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectControl.cs:182 — VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectControl.cs:182-186 | VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/PowerPointControl.cs:154-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectControl.cs:182` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:65 — Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:65-69 | Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py:63-68 — `Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py` and `Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 43 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) REDACTED:143 — REDACTED:143-149 | REDACTED:142-146 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 62 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (11 lines × 2) · ×3

Duplicated block (11 lines × 2) REDACTED:58 — REDACTED:58-68 | REDACTED:62-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED: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.
Duplicated block (11 lines × 2) REDACTED:117 — REDACTED:117-127 | Pix2Story/source/skipthoughts_vectors/training/model.py:16-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 (11 lines × 2) REDACTED:146 — REDACTED:146-156 | REDACTED:51-61 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×3

Duplicated block (5 lines × 3) Pix2Story/source/skipthoughts_vectors/decoding/model.py:77 — Pix2Story/source/skipthoughts_vectors/decoding/model.py:77-81 | Pix2Story/source/skipthoughts_vectors/training/model.py:98-102 | Pix2Story/source/skipthoughts_vectors/training/model.py:111-115 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 3) Pix2Story/source/generate.py:177 — Pix2Story/source/generate.py:177-181 | Pix2Story/source/generate.py:185-189 | Pix2Story/source/generate.py:190-194 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Pix2Story/source/generate.py:182` calls `PoolLayer` and `Pix2Story/source/generate.py:195` 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 (5 lines × 3) VirtualStage/BackgroundMatting/networks.py:24 — VirtualStage/BackgroundMatting/networks.py:24-28 | VirtualStage/BackgroundMatting/networks.py:31-35 | VirtualStage/BackgroundMatting/networks.py:40-44 — 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.

IC1 · Incompleteness & stubs · Empty method body · ×3

Empty method body — does nothing with its inputs Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:42 — `SubmitButtonClickEvent` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:47 — `SubmitApiCallEvent` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs Snip-Insights/SnipInsight/Telemetry/ApplicationLogger.cs:52 — `SubmitStateTransitionEvent` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.

R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×3

Duplicated block (10 lines × 2 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/InstructionBuilder.js:83 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/InstructionBuilder.js:83 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/InstructionBuilder.js:103 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:11 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:11 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/ListCardMapper.js:2 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) JFKFiles/frontend/src/az-api/response.parser.ts:29 — JFKFiles/frontend/src/az-api/response.parser.ts:29 · JFKFiles/frontend/src/graph-api/response.parser.ts:27 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3

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

AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×2

Low contrast colour pair in CSS (4.4:1) BuildAnIntelligentBot/src/ChatBot/wwwroot/styles/app.css:79 — `#applyBtn, #submit-audio` sets color: white on background-color: #0078d7 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.css:6 — `.wc-app button` sets color: #ffffff on background-color: #0078d7 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.

AX2 · Stateful singletons · Stateful singleton · ×2

Stateful singleton: KinectCaptureProvidersFactory VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:8 — `KinectCaptureProvidersFactory` is a singleton (one shared instance) but mutates instance state outside any lock (currentCaptureProviders; e.g. `currentCaptureProviders` at line 29).
Stateful singleton: PowerPointGraphicsCaptureItemsFactory VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:13 — `PowerPointGraphicsCaptureItemsFactory` is a singleton (one shared instance) but mutates instance state outside any lock (currentCaptureItems; e.g. `currentCaptureItems` at line 32).

D17 · Explicit Debt · BareSuppressMessage · ×2

BareSuppressMessage Snip-Insights/SnipInsight/StateMachine/SnipInsightTrigger.cs:7 — SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage Snip-Insights/SnipInsight/Util/LogUploader.cs:189 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

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

REDACTED
REDACTED

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

Duplicated block (20 lines × 2) Snip-Insights/SnipInsight/Email/EmailManager.cs:20 — Snip-Insights/SnipInsight/Email/EmailManager.cs:20-39 | Snip-Insights/SnipInsight/Email/EmailManager.cs:81-100 — 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 `Snip-Insights/SnipInsight/Email/EmailManager.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) REDACTED:42 — REDACTED:42-61 | REDACTED:38-57 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 62 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

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

Duplicated block (8 lines × 3) Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:104 — Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:104-111 | Snip-Insights/SnipInsight/AIServices/AILogic/EntitySearchHandler.cs:73-80 | Snip-Insights/SnipInsight/AIServices/AILogic/ImageSearchHandler.cs:71-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:104` 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, `Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:114` calls `MediaTypeHeaderValue` and `Snip-Insights/SnipInsight/AIServices/AILogic/EntitySearchHandler.cs:84` 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 × 3) REDACTED:142 — REDACTED:142-149 | Pix2Story/source/skipthoughts_vectors/decoding/model.py:51-58 | Pix2Story/source/skipthoughts_vectors/training/model.py:135-142 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Pix2Story/source/skipthoughts_vectors/decoding/model.py:51` calls `matrix` and `REDACTED:142` 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 (9 lines × 2) · ×2

Duplicated block (9 lines × 2) Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageSearchViewModel.cs:136 — Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageSearchViewModel.cs:136-144 | Snip-Insights/SnipInsight/AIServices/AIViewModels/ProductSearchViewModel.cs:141-149 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointHelper.cs:23 — VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointHelper.cs:23-31 | VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointHelper.cs:35-43 — 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 (8 lines × 2) · ×2

Duplicated block (8 lines × 2) Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:249 — Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:249-256 | Snip-Insights/SnipInsight/Util/WinMessage.cs:40-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:249` 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 (8 lines × 2) VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/DecodedKinectCaptureFrame.cs:102 — VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/DecodedKinectCaptureFrame.cs:102-109 | VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/DecodedKinectCaptureFrame.cs:126-133 — 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 `VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/DecodedKinectCaptureFrame.cs:102` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/DecodedKinectCaptureFrame.cs:99` calls `Slice` and `VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/DecodedKinectCaptureFrame.cs:124` 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 (15 lines × 2) · ×2

Duplicated block (15 lines × 2) Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:22 — Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:22-36 | Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py:20-34 — `Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py` and `Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 43 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:48 — Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py:48-62 | Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py:46-60 — `Pix2Story/source/skipthoughts_vectors/decoding/homogeneous_data.py` and `Pix2Story/source/skipthoughts_vectors/training/homogeneous_data.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 43 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Sync-over-async blocking — 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs:181 — `captureEvent.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).

R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×2

Duplicated block (14 lines × 2 locations) JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:66 — JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:66 · JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-preview.component.tsx:91 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) JFKFiles/frontend/src/common/components/logo-jfk/svg.component.tsx:5 — JFKFiles/frontend/src/common/components/logo-jfk/svg.component.tsx:5 · JFKFiles/frontend/src/common/components/logo-microsoft/svg.component.tsx:7 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×2

Duplicated block (11 lines × 2 locations) JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-docnode.component.tsx:70 — JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-docnode.component.tsx:70 · JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-node.component.tsx:79 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (11 lines × 2 locations) JFKFiles/frontend/src/pages/search-page/service/service.ts:12 — JFKFiles/frontend/src/pages/search-page/service/service.ts:12 · JFKFiles/frontend/src/pages/search-page/service/service.ts:27 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

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

Sync-over-async (deadlock risk) through `.Result` Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:62 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` Snip-Insights/SnipInsight/AIServices/AILogic/ContentModerationHandler.cs:101 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.

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

Disposable created and abandoned in the method that made it Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:651 — `myProcess` is a `Process`, which implements `IDisposable`, and it is created here (line 651). Every use of it in `CreateAndOpenICSFile` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var myProcess = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it Snip-Insights/SnipInsight/Views/ToastControl.xaml.cs:46 — `t` is a `Timer`, which implements `IDisposable`, and it is created here (line 46). Every use of it in `Control_Loaded` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var t = …;`), which releases it at the end of the scope on every path including a throw.

AC2 · Forms & labels · <SearchInput> field component without a label · ×1

<SearchInput> field component without a label JFKFiles/frontend/src/pages/home-page/home-page.component.tsx:24 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.

AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×1

Low contrast colour pair in CSS (2.8:1) GoogleAssistantConnector/DemoBot/BotUsingCards/wwwroot/default.htm:8 — `header` sets color: white on background-color: #55A0E0 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.

AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.0 · ×1

Low contrast colour pair in CSS (3.0:1) Sketch2Code/Sketch2Code.Web/Content/bootstrap.css:2761 — `.btn-outline-info:not(:disabled):not(.disabled):active, .btn-outline-info:not(:disabled):not(.disabled).active, .show > .btn-outline-info.dropdown-toggle` sets color: #fff on background-color: #17a2b8 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.

AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.4 · ×1

Low contrast colour pair in CSS (2.4:1) Sketch2Code/Sketch2Code.Web/Content/main.css:94 — `#steps .dot` sets color: #47445a on background-color: grey — 2.4: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 a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 107 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 · jquery-3.0.0.defaultPrefilter (cyclomatic 45) · ×1

jquery-3.0.0.defaultPrefilter (cyclomatic 45) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6660 — jquery-3.0.0.defaultPrefilter has cyclomatic complexity 45 (threshold 15). Of this number, 41 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · background_matting_image.inference (cyclomatic 36) · ×1

background_matting_image.inference (cyclomatic 36) VirtualStage/BackgroundMatting/background_matting_image.py:31 — background_matting_image.inference has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · jquery-3.0.0.jQuery.Callbacks (cyclomatic 30) · ×1

jquery-3.0.0.jQuery.Callbacks (cyclomatic 30) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:3197 — jquery-3.0.0.jQuery.Callbacks has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (fire, a function literal at line 3285, a function literal at line 3275, …). 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. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · jquery-3.0.0.slim.jQuery.Callbacks (cyclomatic 30) · ×1

jquery-3.0.0.slim.jQuery.Callbacks (cyclomatic 30) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:3197 — jquery-3.0.0.slim.jQuery.Callbacks has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (fire, a function literal at line 3285, a function literal at line 3275, …). 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 · RichMessageLimitationsManager.compact (cyclomatic 28) · ×1

RichMessageLimitationsManager.compact (cyclomatic 28) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:11 — RichMessageLimitationsManager.compact has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 20). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · jquery-3.0.0.jQuery.ajaxTransport() (cyclomatic 27) · ×1

jquery-3.0.0.jQuery.ajaxTransport() (cyclomatic 27) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:9234 — jquery-3.0.0.jQuery.ajaxTransport() has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 9240, 9280, 9331, …). 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 file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · jquery-3.0.0.ajaxConvert (cyclomatic 25) · ×1

jquery-3.0.0.ajaxConvert (cyclomatic 25) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:8464 — jquery-3.0.0.ajaxConvert has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · AppManager.DeleteAsync (cyclomatic 22) · ×1

AppManager.DeleteAsync (cyclomatic 22) Snip-Insights/SnipInsight/AppManager.cs:917 — AppManager.DeleteAsync has cyclomatic complexity 22 (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 · KinectCaptureProvider.RenderThread (cyclomatic 22) · ×1

KinectCaptureProvider.RenderThread (cyclomatic 22) VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs:176 — KinectCaptureProvider.RenderThread has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · jquery-3.0.0.adjustCSS (cyclomatic 22) · ×1

jquery-3.0.0.adjustCSS (cyclomatic 22) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4429 — jquery-3.0.0.adjustCSS has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · jquery-3.0.0.domManip (cyclomatic 22) · ×1

jquery-3.0.0.domManip (cyclomatic 22) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5564 — jquery-3.0.0.domManip has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · jquery-3.0.0.slim.adjustCSS (cyclomatic 22) · ×1

jquery-3.0.0.slim.adjustCSS (cyclomatic 22) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4429 — jquery-3.0.0.slim.adjustCSS has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · jquery-3.0.0.slim.domManip (cyclomatic 22) · ×1

jquery-3.0.0.slim.domManip (cyclomatic 22) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:5564 — jquery-3.0.0.slim.domManip has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · OCRViewModel.GetLUISInsights (cyclomatic 20) · ×1

OCRViewModel.GetLUISInsights (cyclomatic 20) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:435 — OCRViewModel.GetLUISInsights has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · KinectD3DImage.RenderThread (cyclomatic 20) · ×1

KinectD3DImage.RenderThread (cyclomatic 20) VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs:80 — KinectD3DImage.RenderThread has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · jquery-3.0.0.buildFragment (cyclomatic 20) · ×1

jquery-3.0.0.buildFragment (cyclomatic 20) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4647 — jquery-3.0.0.buildFragment has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · jquery-3.0.0.slim.buildFragment (cyclomatic 20) · ×1

jquery-3.0.0.slim.buildFragment (cyclomatic 20) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4647 — jquery-3.0.0.slim.buildFragment has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · jquery-3.0.0.jQuery.speed (cyclomatic 19) · ×1

jquery-3.0.0.jQuery.speed (cyclomatic 19) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:7021 — jquery-3.0.0.jQuery.speed has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · jquery-3.0.0.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 18) · ×1

jquery-3.0.0.jQuery.ajaxPrefilter("json jsonp") (cyclomatic 18) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:9462 — jquery-3.0.0.jQuery.ajaxPrefilter("json jsonp") has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · payload.parser.parsePayloadGET (cyclomatic 17) · ×1

payload.parser.parsePayloadGET (cyclomatic 17) JFKFiles/frontend/src/az-api/payload/payload.parser.ts:16 — payload.parser.parsePayloadGET has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · jquery-3.0.0.Animation (cyclomatic 17) · ×1

jquery-3.0.0.Animation (cyclomatic 17) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6866 — jquery-3.0.0.Animation has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (tick, a function literal at line 6921, a function literal at line 6915). 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. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · jquery-3.0.0.ajaxHandleResponses (cyclomatic 16) · ×1

jquery-3.0.0.ajaxHandleResponses (cyclomatic 16) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:8406 — jquery-3.0.0.ajaxHandleResponses has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 11 of the 22 methods over the threshold — including the worst — and 96 of the 190 points over it (51%), 2.8× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 34). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D17 · Explicit Debt · DeadPreprocessorBranch · ×1

DeadPreprocessorBranch Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:323 — #if CHANGE_MAGNIFIER_POSITION — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.

D18 · Solution Shape · Build failed · ×1

Build failed — The target solution did not build cleanly (errors: 20), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: MSB4018: The "Nerdbank.GitVersioning.Tasks.GetBuildVersion" task failed unexpectedly.; MSB4018: System.TypeInitializationException: The type initializer for 'LibGit2Sharp.Core.NativeMethods' threw an exception.; MSB4018: ---> System.DllNotFoundException: Unable to load shared library '/root/.nuget/packages/nerdbank.gitversioning/2.1.23/build/MSBuildFull/lib/linux/x86_64/libgit2-1196807.so' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:; MSB4018: libssl.so.1.0.0: cannot open shared object file: No such file or directory; MSB4018: [Snip-Insights/SnipInsight.Forms/SnipInsight.Forms.csproj]; MSB3073: The command "taskkill /IM "Snip Insights.exe" /FI "STATUS eq RUNNING" /F" exited with code 127.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/WindowsXaml/v18.0/Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath)/Microsoft/WindowsXaml/v$(VisualStudioVersion)/Microsoft.Windows.UI.Xaml.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400//Microsoft/WindowsXaml/v18.0/Microsoft.Windows.UI.Xaml.CSharp.targets", is correct, and that the file exists on disk.; CS0234: The type or namespace name 'PersonalityChat' does not exist in the namespace 'Microsoft.Bot.Builder' (are you missing an assembly reference?); CS0246: The type or namespace name 'PersonalityChatResults' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'PersonalityChatService' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'PersonalityChatMiddlewareOptions' could not be found (are you missing a using directive or an assembly reference?); CS0234: The type or namespace name 'Azure' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0234: The type or namespace name 'WindowsAzure' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?); CS0246: The type or namespace name 'Newtonsoft' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'ISearchServiceClient' could not be found (are you missing a using directive or an assembly reference?).

D18 · Solution Shape · Solution references 2 projects that do not exist · ×1

Solution references 2 projects that do not exist Sketch2Code/Sketch2Code.sln — `Sketch2Code/Sketch2Code.sln` declares 2 project file(s) that are missing from the tree (`Sketch2Code/BoxGeometryTest/BoxGeometryTest.csproj`, `Sketch2Code/GeometryUI/GeometryUI.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.

D2 · Cognitive Complexity · jquery-3.0.0.defaultPrefilter (cognitive 81) · ×1

jquery-3.0.0.defaultPrefilter (cognitive 81) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6660 — jquery-3.0.0.defaultPrefilter has cognitive complexity 81 (threshold 15). Drivers by points: if/else 27 (64 pts), boolean chains 12, loops 3 (5 pts) (nesting depth added 39). Of this number, 73 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · background_matting_image.inference (cognitive 75) · ×1

background_matting_image.inference (cognitive 75) VirtualStage/BackgroundMatting/background_matting_image.py:31 — background_matting_image.inference has cognitive complexity 75 (threshold 15). Drivers by points: if/else 27 (62 pts), loops 4 (8 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · jquery-3.0.0.ajaxConvert (cognitive 73) · ×1

jquery-3.0.0.ajaxConvert (cognitive 73) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:8464 — jquery-3.0.0.ajaxConvert has cognitive complexity 73 (threshold 15). Drivers by points: if/else 14 (47 pts), loops 3 (8 pts), ternaries 1 (7 pts), error handling 1 (6 pts), boolean chains 5 (nesting depth added 49). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.domManip (cognitive 51) · ×1

jquery-3.0.0.domManip (cognitive 51) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5564 — jquery-3.0.0.domManip has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (39 pts), loops 2 (7 pts), boolean chains 5 (nesting depth added 32). Of this number, 49 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.domManip (cognitive 51) · ×1

jquery-3.0.0.slim.domManip (cognitive 51) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:5564 — jquery-3.0.0.slim.domManip has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (39 pts), loops 2 (7 pts), boolean chains 5 (nesting depth added 32). Of this number, 49 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · KinectCaptureProvider.RenderThread (cognitive 49) · ×1

KinectCaptureProvider.RenderThread (cognitive 49) VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvider.cs:176 — KinectCaptureProvider.RenderThread has cognitive complexity 49 (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 · RichMessageLimitationsManager.compact (cognitive 48) · ×1

RichMessageLimitationsManager.compact (cognitive 48) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:11 — RichMessageLimitationsManager.compact has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (40 pts), boolean chains 5, loops 1 (2 pts), match/switch 1 (nesting depth added 22). Of this number, 22 points are the body's own statements and 26 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · KinectD3DImage.RenderThread (cognitive 42) · ×1

KinectD3DImage.RenderThread (cognitive 42) VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs:80 — KinectD3DImage.RenderThread has cognitive complexity 42 (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 · jquery-3.0.0.buildFragment (cognitive 39) · ×1

jquery-3.0.0.buildFragment (cognitive 39) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4647 — jquery-3.0.0.buildFragment has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 4 (9 pts), boolean chains 6, ternaries 1 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.buildFragment (cognitive 39) · ×1

jquery-3.0.0.slim.buildFragment (cognitive 39) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4647 — jquery-3.0.0.slim.buildFragment has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 4 (9 pts), boolean chains 6, ternaries 1 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · jquery-3.0.0.jQuery.Callbacks (cognitive 38) · ×1

jquery-3.0.0.jQuery.Callbacks (cognitive 38) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:3197 — jquery-3.0.0.jQuery.Callbacks has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 7, loops 3 (4 pts), ternaries 1 (nesting depth added 11). None of this is in the body itself: all 38 points belong to 8 function items inside it that branch (fire, a function literal at line 3275, a function literal at line 3285, …). 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. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.jQuery.Callbacks (cognitive 38) · ×1

jquery-3.0.0.slim.jQuery.Callbacks (cognitive 38) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:3197 — jquery-3.0.0.slim.jQuery.Callbacks has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 7, loops 3 (4 pts), ternaries 1 (nesting depth added 11). None of this is in the body itself: all 38 points belong to 8 function items inside it that branch (fire, a function literal at line 3275, a function literal at line 3285, …). 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 · Geometry.RemoveOverlappingOld (cognitive 36) · ×1

Geometry.RemoveOverlappingOld (cognitive 36) Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:276 — Geometry.RemoveOverlappingOld has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D2 · Cognitive Complexity · AppManager.DeleteAsync (cognitive 35) · ×1

AppManager.DeleteAsync (cognitive 35) Snip-Insights/SnipInsight/AppManager.cs:917 — AppManager.DeleteAsync has cognitive complexity 35 (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 · jquery-3.0.0.jQuery.ajaxTransport() (cognitive 31) · ×1

jquery-3.0.0.jQuery.ajaxTransport() (cognitive 31) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:9234 — jquery-3.0.0.jQuery.ajaxTransport() has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 9, loops 2 (5 pts), error handling 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 9240, 9365, 9280, …). 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 file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.access (cognitive 27) · ×1

jquery-3.0.0.access (cognitive 27) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:3870 — jquery-3.0.0.access has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 4 (10 pts), loops 2 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.access (cognitive 27) · ×1

jquery-3.0.0.slim.access (cognitive 27) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:3870 — jquery-3.0.0.slim.access has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 4 (10 pts), loops 2 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · jquery-3.0.0.ajaxHandleResponses (cognitive 26) · ×1

jquery-3.0.0.ajaxHandleResponses (cognitive 26) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:8406 — jquery-3.0.0.ajaxHandleResponses has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · FacetGraphGenerator.GetFacetGraphNodes (cognitive 25) · ×1

FacetGraphGenerator.GetFacetGraphNodes (cognitive 25) JFKFiles/JfkWebApiSkills/JfkWebApiSkills/AzureSearch/FacetGraphGenerator.cs:17 — FacetGraphGenerator.GetFacetGraphNodes has cognitive complexity 25 (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 · jquery-3.0.0.showHide (cognitive 24) · ×1

jquery-3.0.0.showHide (cognitive 24) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4513 — jquery-3.0.0.showHide has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 2, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.showHide (cognitive 24) · ×1

jquery-3.0.0.slim.showHide (cognitive 24) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4513 — jquery-3.0.0.slim.showHide has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), boolean chains 2, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · OCRViewModel.GetLUISInsights (cognitive 22) · ×1

OCRViewModel.GetLUISInsights (cognitive 22) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:435 — OCRViewModel.GetLUISInsights has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LogUploader.Send (cognitive 21) · ×1

LogUploader.Send (cognitive 21) Snip-Insights/SnipInsight/Util/LogUploader.cs:113 — LogUploader.Send has cognitive complexity 21 (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 · jquery-3.0.0.Animation (cognitive 21) · ×1

jquery-3.0.0.Animation (cognitive 21) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6866 — jquery-3.0.0.Animation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, loops 3, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (tick, a function literal at line 6921, a function literal at line 6915). 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. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · AppUpdaterService.CheckAndUpdate (cognitive 20) · ×1

AppUpdaterService.CheckAndUpdate (cognitive 20) VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/AppUpdaterService.cs:50 — AppUpdaterService.CheckAndUpdate has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D2 · Cognitive Complexity · jquery-3.0.0.adjustCSS (cognitive 19) · ×1

jquery-3.0.0.adjustCSS (cognitive 19) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4429 — jquery-3.0.0.adjustCSS has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 3 (4 pts), loops 1 (2 pts), ternaries 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.adjustCSS (cognitive 19) · ×1

jquery-3.0.0.slim.adjustCSS (cognitive 19) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4429 — jquery-3.0.0.slim.adjustCSS has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 3 (4 pts), loops 1 (2 pts), ternaries 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · AriModernWindow.OnApplyTemplate (cognitive 18) · ×1

AriModernWindow.OnApplyTemplate (cognitive 18) Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.cs:32 — AriModernWindow.OnApplyTemplate has cognitive complexity 18 (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 · HocrPage.HocrPage.ctor (cognitive 18) · ×1

HocrPage.HocrPage.ctor (cognitive 18) JFKFiles/JfkWebApiSkills/JfkWebApiSkills/HocrGenerator/HocrDocument.cs:41 — HocrPage.HocrPage.ctor has cognitive complexity 18 (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 · fixed_threshold.fixed_split (cognitive 18) · ×1

fixed_threshold.fixed_split (cognitive 18) VirtualStage/BackgroundMatting/fixed_threshold.py:4 — fixed_threshold.fixed_split has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · prepare_data.prepare_videos (cognitive 18) · ×1

prepare_data.prepare_videos (cognitive 18) VirtualStage/BackgroundMatting/prepare_data.py:4 — prepare_data.prepare_videos has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · jquery-3.0.0.augmentWidthOrHeight (cognitive 18) · ×1

jquery-3.0.0.augmentWidthOrHeight (cognitive 18) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6135 — jquery-3.0.0.augmentWidthOrHeight has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.augmentWidthOrHeight (cognitive 18) · ×1

jquery-3.0.0.slim.augmentWidthOrHeight (cognitive 18) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:6135 — jquery-3.0.0.slim.augmentWidthOrHeight has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ImageAnalysisViewModel.GetCelebrities (cognitive 17) · ×1

ImageAnalysisViewModel.GetCelebrities (cognitive 17) Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:170 — ImageAnalysisViewModel.GetCelebrities has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Geometry.DeleteOverlapping (cognitive 17) · ×1

Geometry.DeleteOverlapping (cognitive 17) Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.cs:242 — Geometry.DeleteOverlapping has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · OCRViewModel.CompareResult (cognitive 16) · ×1

OCRViewModel.CompareResult (cognitive 16) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:326 — OCRViewModel.CompareResult has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D2 · Cognitive Complexity · ToolWindow.OnIsOpenChanged (cognitive 16) · ×1

ToolWindow.OnIsOpenChanged (cognitive 16) Snip-Insights/SnipInsight/Views/ToolWindow.xaml.cs:163 — ToolWindow.OnIsOpenChanged has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SmartBoundaryDetection.GetTopElement (cognitive 16) · ×1

SmartBoundaryDetection.GetTopElement (cognitive 16) Snip-Insights/SnipInsight/ImageCapture/SmartBoundaryDetection.cs:105 — SmartBoundaryDetection.GetTopElement has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CarouselCardMapper._buildCarouselCard (cognitive 16) · ×1

CarouselCardMapper._buildCarouselCard (cognitive 16) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:26 — CarouselCardMapper._buildCarouselCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (5 pts), boolean chains 2, 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 · payload.parser.parsePayloadGET (cognitive 16) · ×1

payload.parser.parsePayloadGET (cognitive 16) JFKFiles/frontend/src/az-api/payload/payload.parser.ts:16 — payload.parser.parsePayloadGET has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 16. 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 · jquery-3.0.0.on (cognitive 16) · ×1

jquery-3.0.0.on (cognitive 16) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4786 — jquery-3.0.0.on has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.propFilter (cognitive 16) · ×1

jquery-3.0.0.propFilter (cognitive 16) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6829 — jquery-3.0.0.propFilter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.jQuery.ajaxPrefilter("json jsonp") (cognitive 16) · ×1

jquery-3.0.0.jQuery.ajaxPrefilter("json jsonp") (cognitive 16) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:9462 — jquery-3.0.0.jQuery.ajaxPrefilter("json jsonp") has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5 (nesting depth added 4). Of this number, 8 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js holds 15 of the 44 methods over the threshold — including the worst — and 271 of the 627 points over it (43%), 2.4× the next-largest file (Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js at 112). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · jquery-3.0.0.slim.on (cognitive 16) · ×1

jquery-3.0.0.slim.on (cognitive 16) Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js:4786 — jquery-3.0.0.slim.on has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

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

REDACTED

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

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

Near-duplicate member pair (56 shared lines) REDACTED:31 — REDACTED:31-157 | REDACTED:31-151 — These two members are variants of one another: 56 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 · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (4 members, 50+ identical tokens) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:520 — Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:520-555 | Snip-Insights/SnipInsight/Email/EmailManager.cs:19-74 | Snip-Insights/SnipInsight/Email/EmailManager.cs:80-154 | Snip-Insights/SnipInsight/Email/EmailManager.cs:161-217 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

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

Duplicated block (21 lines × 2) Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs:211 — Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs:211-231 | Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.cs:237-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.

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

Duplicated block (22 lines × 3) Snip-Insights/SnipInsight/Email/EmailManager.cs:47 — Snip-Insights/SnipInsight/Email/EmailManager.cs:47-68 | Snip-Insights/SnipInsight/Email/EmailManager.cs:126-147 | Snip-Insights/SnipInsight/Email/EmailManager.cs:196-217 — 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 `Snip-Insights/SnipInsight/Email/EmailManager.cs:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

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

Duplicated block (15–22 lines × 2) Snip-Insights/SnipInsight/ImageCapture/DpiScalor.cs:26 — Snip-Insights/SnipInsight/ImageCapture/DpiScalor.cs:26-40 | Snip-Insights/SnipInsight/Util/DpiUtilities.cs:276-297 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Duplicated block (21–22 lines × 2) Snip-Insights/SnipInsight/Util/NativeMethods.cs:49 — Snip-Insights/SnipInsight/Util/NativeMethods.cs:49-70 | VirtualStage/Speaker.Recorder/Speaker.Recorder/Helpers/WindowHelper.cs:44-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Snip-Insights/SnipInsight/Util/NativeMethods.cs:49` 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 (18 lines × 2) · ×1

Duplicated block (18 lines × 2) Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:44 — Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:44-61 | Sketch2Code/Sketch2Code.Web/Controllers/TemplateController.cs:54-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:44` 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.

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

Duplicated block (15–16 lines × 2) VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/GraphicsItemD3DImage.cs:155 — VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/GraphicsItemD3DImage.cs:155-170 | VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.cs:244-258 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/GraphicsItemD3DImage.cs:155` 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 (14 lines × 2) · ×1

Duplicated block (14 lines × 2) BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:26 — BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:26-39 | BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:52-65 — 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 `BuildAnIntelligentBot/src/ChatBot/Services/TranslatorTextService.cs:26` 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 × 4) · ×1

Duplicated block (7 lines × 4) Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:534 — Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:534-540 | Snip-Insights/SnipInsight/Email/EmailManager.cs:47-53 | Snip-Insights/SnipInsight/Email/EmailManager.cs:126-132 | Snip-Insights/SnipInsight/Email/EmailManager.cs:196-202 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.

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

Duplicated block (26 lines × 2) REDACTED:19 — REDACTED:19-44 | REDACTED:24-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:19` 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 (23 lines × 2) · ×1

Duplicated block (23 lines × 2) REDACTED:181 — REDACTED:181-203 | REDACTED:90-112 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:115` calls `_step`, `pref` and `REDACTED:205` 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 (17–19 lines × 2) · ×1

Duplicated block (17–19 lines × 2) REDACTED:64 — REDACTED:64-82 | REDACTED:56-72 — `REDACTED` and `REDACTED` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 62 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:86` calls `pre_emb` and `REDACTED:75` does not — after which the two agree again for 4 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 (18 lines × 3) · ×1

Duplicated block (18 lines × 3) MachineTeaching/Machine-Calibration/cnc_simulator.py:61 — MachineTeaching/Machine-Calibration/cnc_simulator.py:61-78 | MachineTeaching/Motion-Control/drill_simulator.py:60-77 | MachineTeaching/Smart-Building/hvac_simulator.py:71-88 — 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.

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

Duplicated block (10–11 lines × 2) VirtualStage/BackgroundMatting/networks.py:212 — VirtualStage/BackgroundMatting/networks.py:212-222 | VirtualStage/BackgroundMatting/networks.py:228-237 — 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 `VirtualStage/BackgroundMatting/networks.py:212` 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–8 lines × 2) · ×1

Duplicated block (7–8 lines × 2) Pix2Story/source/training/train_decoder.py:17 — Pix2Story/source/training/train_decoder.py:17-24 | REDACTED:31-37 — 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 before the matched lines, `Pix2Story/source/training/train_decoder.py:15` calls `load_model` and `REDACTED:30` 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 (13 lines × 3) · ×1

Duplicated block (13 lines × 3) MachineTeaching/Machine-Calibration/cnc_simulator.py:81 — MachineTeaching/Machine-Calibration/cnc_simulator.py:81-93 | MachineTeaching/Motion-Control/drill_simulator.py:80-92 | MachineTeaching/Smart-Building/hvac_simulator.py:91-103 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D8 · Code Coverage · Coverage not measured · ×1

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

IC1 · Incompleteness & stubs · Hollow method · ×1

Hollow method — returns a constant without doing the work Snip-Insights/SnipInsight/Views/ControlTreeEnumerator.cs:51 — `GetContent` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.

IC1 · Incompleteness & stubs · Markup wires an event to an empty handler · ×1

Markup wires an event to an empty handler Snip-Insights/SnipInsight/Views/SettingsPanel.xaml.cs:94 — `SettingsPanel.xaml` wires an event to `ScreenCaptureKeyCombo_KeyComboChanged`, whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.

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.

R10 · Code Duplication · Duplicated block with local edits (31 matched lines × 2 locations) · ×1

Duplicated block with local edits (31 matched lines × 2 locations) JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:113 — JFKFiles/frontend/src/common/components/hocr/hocr-document/hocr-document.component.tsx:113 · JFKFiles/frontend/src/common/components/hocr/hocr-preview/hocr-preview.component.tsx:149 — the two spans are one implementation copied and then locally edited — 210 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1

Duplicated block (25 lines × 2 locations) JFKFiles/frontend/src/az-api/api.ts:13 — JFKFiles/frontend/src/az-api/api.ts:13 · JFKFiles/frontend/src/graph-api/api.ts:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

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

Duplicated block (22 lines × 2 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:22 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:22 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:70 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1

Duplicated block (20 lines × 2 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:75 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.

R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1

Duplicated block (16 lines × 2 locations) JFKFiles/frontend/src/pages/search-page/components/selection-controls/checkbox-list.component.tsx:11 — JFKFiles/frontend/src/pages/search-page/components/selection-controls/checkbox-list.component.tsx:11 · JFKFiles/frontend/src/pages/search-page/components/selection-controls/year-picker.component.tsx:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) · ×1

Duplicated block with local edits (13 matched lines × 2 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:32 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:32 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:47 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1

Duplicated block (12 lines × 2 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:52 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:52 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

R10 · Code Duplication · Duplicated block (11 lines × 3 locations) · ×1

Duplicated block (11 lines × 3 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:76 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:75 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/SuggestedActionsMapper.js:31 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×1

Duplicated block (6 lines × 2 locations) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/Trace.js:23 — GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/Trace.js:23 · GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/Trace.js:35 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

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

Duplicated block (5 lines × 2 locations) JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts:168 — JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts:168 · JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts:180 — 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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 20, cognitive 26) · ×1

Complex function (anonymous) (cyclomatic 20, cognitive 26) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/googleActions/RichMessageLimitationsManager.js:20 — (anonymous) has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 16) · ×1

Complex function (anonymous) (cyclomatic 17, cognitive 16) JFKFiles/frontend/src/az-api/payload/payload.parser.ts:16 — (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function _buildCarouselCard (cyclomatic 11, cognitive 15) · ×1

Complex function _buildCarouselCard (cyclomatic 11, cognitive 15) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/CarouselCardMapper.js:26 — _buildCarouselCard has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function _buildBasicCard (cyclomatic 11, cognitive 14) · ×1

Complex function _buildBasicCard (cyclomatic 11, cognitive 14) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/BasicCardMapper.js:27 — _buildBasicCard has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function _buildBasicCard (cyclomatic 11, cognitive 13) · ×1

Complex function _buildBasicCard (cyclomatic 11, cognitive 13) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/MediaCardMapper.js:75 — _buildBasicCard has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R4 · Test Coverage · Test Coverage · ×1

Test Coverage — 0% of 113 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

R6 · Tooling · No test, lint or typecheck script · ×1

No test, lint or typecheck script — test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

R7 · Dead Code · Dead file (~32 LoC) · ×1

Dead file (~32 LoC) GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/global/conversationQueue.js — no import path from any entry point (4 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~10 LoC) · ×1

Dead file (~10 LoC) JFKFiles/frontend/server/index.js — no import path from any entry point (4 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~0 LoC) · ×1

Dead file (~0 LoC) JFKFiles/frontend/src/common/components/pagination/index.ts — no import path from any entry point (4 application, 4 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1

Third-party script without Subresource Integrity Sketch2Code/Sketch2Code.Web/Maqueta/CarrouselTest.html:10 — `https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 16 such include(s) across the repository's markup.

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

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

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

Sync-over-async (deadlock risk) through `Task.WaitAny` BuildAnIntelligentBot/src/ChatBot/Services/TranslatorSpeechService.cs:81 — `Task.WaitAny` blocks this thread until the tasks complete — sync-over-async: it can deadlock under a synchronization context and it parks a thread for as long as the work runs. `await Task.WhenAny(…)` instead.

X1 · Async correctness · Blocking `Thread.Sleep` inside an `async` method · ×1

Blocking `Thread.Sleep` inside an `async` method JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:251 — `Thread.Sleep` parks the thread for the whole delay: no other work runs on it, and under load the pool must grow to make up for it. `await Task.Delay(…)` suspends only this method.

X3 · Exception handling · Rethrow loses stack trace (`throw ex;`) · ×1

Rethrow loses stack trace (`throw ex;`) Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs:60 — `throw e;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.

Minor — 310 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×159

Orphaned file Snip-Insights/SnipInsight/ViewModels/SnipInsightViewModel.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 Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.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 Snip-Insights/SnipInsight/Views/ToolWindow.xaml.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 Snip-Insights/SnipInsight/StateMachine/StateMachine.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 Snip-Insights/SnipInsight.Forms/Features/Insights/OCR/OCRViewModel.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 Snip-Insights/SnipInsight/Views/SettingsPanel.xaml.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 Snip-Insights/SnipInsight.Forms.GTK/Controls/CanvasDrawingArea.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 Snip-Insights/SnipInsight/ImageCapture/SmartBoundaryDetection.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 JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.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 Snip-Insights/SnipInsight/Views/MainWindow.xaml.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 Sketch2Code/Sketch2Code.Core/Entities/BoxGeometry/Geometry.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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.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 Sketch2Code/Sketch2Code.Core/Services/ObjectDetectionAppService.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 Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.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 VirtualStage/Speaker.Recorder/Speaker.Recorder/ViewModels/RecordViewModel.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 Snip-Insights/SnipInsight/Email/EmailManager.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 Snip-Insights/SnipInsight/Views/LayoutUtilities.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 Snip-Insights/SnipInsight/ViewModels/AIPanelViewModel.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 VirtualStage/Speaker.Recorder/Speaker.Recorder/Controls/KinectD3DImage.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 Snip-Insights/SnipInsight/Controls/Ariadne/AriModernWindow.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 Snip-Insights/SnipInsight/Util/AnimationUtilities.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 Snip-Insights/SnipInsight/Util/DpiUtilities.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.
+ 134 more in this group — see findings.md.

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

Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:25 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:28 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:45 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Kinect/KinectCaptureProvidersFactory.cs:56 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/RecordingSession.cs:56 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/RecordingSession.cs:75 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/RecordingSession.cs:86 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:219 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:249 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:262 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:327 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:338 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:361 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:364 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:380 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Models/Session.cs:383 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:28 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:31 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:70 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:87 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/PowerPoint/PowerPointGraphicsCaptureItemsFactory.cs:94 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/AppUpdaterService.cs:56 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/AppUpdaterService.cs:66 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/AppUpdaterService.cs:77 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging VirtualStage/Speaker.Recorder/Speaker.Recorder/Services/KinectRecorderService.cs:44 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
+ 15 more in this group — see findings.md.

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

Commented-out code GoogleAssistantConnector/DemoBot/BotUsingCards/Program.cs:27 — 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 GoogleAssistantConnector/DemoBot/BotUsingCards/Program.cs:28 — 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 GoogleAssistantConnector/DemoBot/BotUsingCards/Startup.cs:104 — 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 GoogleAssistantConnector/DemoBot/BotUsingCards/Startup.cs:105 — 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 GoogleAssistantConnector/DemoBot/BotUsingCards/Startup.cs:108 — 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 GoogleAssistantConnector/DemoBot/BotUsingCards/Startup.cs:111 — 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 GoogleAssistantConnector/DemoBot/BotUsingCards/Startup.cs:112 — 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 GoogleAssistantConnector/DemoBot/BotUsingCards/Startup.cs:113 — 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 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:121 — 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 Sketch2Code/Sketch2Code.Web/Controllers/AppController.cs:124 — 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 Snip-Insights/SnipInsight/AIServices/AIManager.cs:38 — 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 Snip-Insights/SnipInsight/AIServices/AIViewModels/ImageAnalysisViewModel.cs:216 — 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 Snip-Insights/SnipInsight/AppManager.cs:371 — 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 Snip-Insights/SnipInsight/Controls/Ariadne/AriMenuItemBase.cs:57 — 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 Snip-Insights/SnipInsight/Controls/Ariadne/AriMenuItemBase.cs:61 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureCursor.cs:44 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureManager.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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:93 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:156 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:157 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:158 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:159 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:296 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:297 — 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 Snip-Insights/SnipInsight/ImageCapture/ImageCaptureWindow.xaml.cs:298 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
+ 1 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×25

Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js:1557 — `!!options.flipVariations && (isVertical && variation === 'start' && overflowsLeft || isVertical && variation === 'end' && overflowsRight || …` appears character-identically in 3 files — Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/umd/popper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2479 — `!context && elem.ownerDocument !== document` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2669 — `!context || rsibling.test( selector ) && testContext( context.parentNode ) || context` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1141 — `!document.getElementsByName || !document.getElementsByName( expando ).length` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:1991 — `!document.hasFocus || document.hasFocus()` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6275 — `!elem || elem.nodeType === 3 || elem.nodeType === 8 || !elem.style` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4977 — `!elemData || !( events = elemData.events )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js:597 — `!element || !element.parentElement || isIE()` appears character-identically in 4 files — Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/umd/popper-utils.js, Sketch2Code/Sketch2Code.Web/Scripts/umd/popper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js:257 — `!element1 || !element1.nodeType || !element2 || !element2.nodeType` appears character-identically in 4 files — Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/umd/popper-utils.js, Sketch2Code/Sketch2Code.Web/Scripts/umd/popper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5081 — `!event.rnamespace || event.rnamespace.test( handleObj.namespace )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5385 — `!event.which && button !== undefined && rmouseEvent.test( event.type )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:6318 — `!hooks || !( "set" in hooks ) || ( value = hooks.set( elem, value, extra ) ) !== undefined` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:7792 — `!hooks || !( "set" in hooks ) || hooks.set( this, val, "value" ) === undefined` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2715 — `!isXML && elem.nodeName.toLowerCase() === "input"` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2410 — `!leadingRelative && ( xml || context !== outermostContext )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2135 — `!matched || (match = rcomma.exec( soFar ))` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js:210 — `!nodeName || nodeName === 'BODY' || nodeName === 'HTML'` appears character-identically in 4 files — Sketch2Code/Sketch2Code.Web/Scripts/esm/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/popper.js, Sketch2Code/Sketch2Code.Web/Scripts/umd/popper-utils.js, Sketch2Code/Sketch2Code.Web/Scripts/umd/popper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:302 — `!obj || toString.call( obj ) !== "[object Object]"` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:8010 — `!onlyHandlers && !event.isDefaultPrevented()` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:7966 — `!onlyHandlers && !special.noBubble && !jQuery.isWindow( elem )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:7960 — `!onlyHandlers && special.trigger && special.trigger.apply( elem, data ) === false` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4639 — `!refElements || dataPriv.get( refElements[ i ], "globalEval" )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:5419 — `!related || ( related !== target && !jQuery.contains( target, related ) )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:2606 — `!seed && tokenize( (selector = compiled.selector || selector) )` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js:4939 — `!special.setup || special.setup.call( elem, data, namespaces, eventHandle ) === false` appears character-identically in 2 files — Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.js, Sketch2Code/Sketch2Code.Web/Scripts/jquery-3.0.0.slim.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

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

README/code drift JFKFiles/README.md:302 — JFKFiles/README.md documents the environment variable `MSDEPLOY_RENAME_LOCKED_FILES`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GoogleAssistantConnector/docs/googleAssistantProxy.settings.es.md:2 — GoogleAssistantConnector/docs/googleAssistantProxy.settings.es.md links to `otherSettings.md`, but `GoogleAssistantConnector/docs/otherSettings.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift GoogleAssistantConnector/DemoBot/BotUsingCards/README.md:36 — GoogleAssistantConnector/DemoBot/BotUsingCards/README.md links to `../../../Installing_CLI_tools.md`, but `Installing_CLI_tools.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Sketch2Code/Sketch2Code.Web/Scripts/README.md:56 — Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/docs/_includes/popper-documentation.md`, but `docs/_includes/popper-documentation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Sketch2Code/Sketch2Code.Web/Scripts/README.md:68 — Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/docs/_includes/tooltip-documentation.md`, but `docs/_includes/tooltip-documentation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Sketch2Code/Sketch2Code.Web/Scripts/README.md:76 — Sketch2Code/Sketch2Code.Web/Scripts/README.md installs `popper.js` (`npm install popper.js --save`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Sketch2Code/Sketch2Code.Web/Scripts/README.md:87 — Sketch2Code/Sketch2Code.Web/Scripts/README.md installs `tooltip.js` (`npm install tooltip.js --save`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Sketch2Code/Sketch2Code.Web/Scripts/README.md:147 — Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `docs/_includes/popper-documentation.md#modifiers--object`, but `Sketch2Code/Sketch2Code.Web/Scripts/docs/_includes/popper-documentation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Sketch2Code/Sketch2Code.Web/Scripts/README.md:159 — Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `/MENTIONS.md`, but `MENTIONS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Sketch2Code/Sketch2Code.Web/Scripts/README.md:219 — Sketch2Code/Sketch2Code.Web/Scripts/README.md links to `LICENSE.md`, but `Sketch2Code/Sketch2Code.Web/Scripts/LICENSE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

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

Silent fallback default in catch JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:95 — `DeleteIndexingResources` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:126 — `CreateSkillSet` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:164 — `CreateIndex` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:196 — `CreateIndexer` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch JFKFiles/JfkWebApiSkills/JfkInitializer/Program.cs:265 — `DeployWebsite` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.

D30 · Dependency Vulnerabilities · Low CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

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

REDACTED
REDACTED
REDACTED
REDACTED

D19 · Documentation Quality · Documentation · ×3

Documentation: no project overview README.md — The README begins with a strong overview of AI Lab and its nine projects but does not state what the project is or what it does in any clear sentence. State the purpose of the repository (AI lab for developers) and what each lab addresses, so readers can find the one that interests them without scanning.
Documentation: no installation or build instructions README.md — The 'Setup your environment' section is long but does not give install commands or a single concise installation line. Add an Install/Build command (e.g. dotnet restore/publish) and any prerequisites so the one-line install note is self-contained.
Documentation: no usage examples README.md — The 'Setup your environment' section explains setup but there are no usage examples showing how to run the lab. Add a short Usage section or an untagged fenced block demonstrating the lab's output (e.g. running the sample Contoso Restaurant bot).

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

Most significant orphaned file Snip-Insights/SnipInsight/AppManager.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Snip-Insights/SnipInsight/Util/NativeMethods.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Snip-Insights/SnipInsight/Util/RegistrySettings.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.

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

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 BuildAnIntelligentBot/src/ChatBot/Program.cs:14 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected GoogleAssistantConnector/DemoBot/BotUsingCards/Program.cs:18 — 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.

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

REDACTED
REDACTED

IC1 · Incompleteness & stubs · Placeholder data left in code · ×2

Placeholder data left in code REDACTED:323 — 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 Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:526 — A placeholder e-mail address ("youremail@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D21 · Naming Consistency · The configuration setting for fallback endpoints is named inconsistently. The property uses the clean name 'FallbackEndpoints', while the backing field uses a redundant suffix '_fallbackEndpointsName'. The suffix 'Name' is unnecessary as the property itself identifies the setting, and it differs from the property name it backs. · ×1

The configuration setting for fallback endpoints is named inconsistently. The property uses the clean name 'FallbackEndpoints', while the backing field uses a redundant suffix '_fallbackEndpointsName'. The suffix 'Name' is unnecessary as the property itself identifies the setting, and it differs from the property name it backs. — Rename the field to '_fallbackEndpoints' to match the property name, or remove the field if not strictly required by serialization patterns. (symbols: Field: private string SnipInsight.Util.UserSettings._fallbackEndpointsName, Property: internal string SnipInsight.Util.UserSettings.FallbackEndpoints)

D21 · Naming Consistency · Spelling inconsistency in the word 'scale'. The field '_scalor' is a misspelling of 'scalar' or 'scale', but given the type is `DpiScale`, it is clearly intended to be 'scale'. Additionally, the resource string 'Screenshot_saved' uses an underscore separator, while other resource strings like 'TrayIcon_BalloonTip_AppIsStillRunning_Title' use underscores, but the field name uses a camelCase prefix with an underscore, which is inconsistent with the general naming style of other private fields in the codebase (e.g., `_instance`, `_actions`). However, the primary issue is the typo 'scalor' vs 'scale'. · ×1

Spelling inconsistency in the word 'scale'. The field '_scalor' is a misspelling of 'scalar' or 'scale', but given the type is `DpiScale`, it is clearly intended to be 'scale'. Additionally, the resource string 'Screenshot_saved' uses an underscore separator, while other resource strings like 'TrayIcon_BalloonTip_AppIsStillRunning_Title' use underscores, but the field name uses a camelCase prefix with an underscore, which is inconsistent with the general naming style of other private fields in the codebase (e.g., `_instance`, `_actions`). However, the primary issue is the typo 'scalor' vs 'scale'. — Rename the field to '_scale' to correct the spelling and align with the type `DpiScale`. (symbols: Field: private DpiScale SnipInsight.ImageCapture.ImageCaptureWindow._scalor, Property: public string SnipInsight.Properties.Resources.Screenshot_saved)

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 1 of 13 project(s) overshoot their size bounds, lowering Project Cohesion to 8.5/10. The most over is `SnipInsight` (19379 LoC, 181 public types across 19 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.

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

REDACTED

D34 · Knowledge Freshness · Dormant codebase · ×1

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

D40 · Network Egress Confinement · No network policy · ×1

No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.

D41 · Kernel & Syscall Confinement · No seccomp profile · ×1

No seccomp profile REDACTED:2 — The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.

GD1 · Unfinished & placeholder code · Placeholder literal left in code · ×1

Placeholder literal left in code Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:526 — A placeholder string ("youremail@example.com") is still in shipped code — typical of generated boilerplate that was never filled in.

M2 · Architecture documentation · No ADRs · ×1

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

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

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

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

No tests/ separation — Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.

M3 · Folder & project structure · Inconsistent root namespaces · ×1

Inconsistent root namespaces — Only 5/13 projects share a common root namespace — the code's module identity is inconsistent.

P2 · Observability · Logging is not universal · ×1

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

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

Console output used as the logging channel Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs:58 — `Snip-Insights/SnipInsight/AIServices/AILogic/HandWrittenTextHandler.cs` reports through `Console.Write…` at line 58 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.

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.

P6 · Release Hygiene · No changelog · ×1

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

R7 · Dead Code · Unused export 'defaultGraphPayload' · ×1

Unused export 'defaultGraphPayload' JFKFiles/frontend/src/graph-api/payload.model.ts:10 — Nothing ultimately consumes this binding: its only referrer is the re-export in JFKFiles/frontend/src/graph-api/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in JFKFiles/frontend/src/graph-api/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'consoleDebug' · ×1

Unused export 'consoleDebug' JFKFiles/frontend/src/util/log-debug.helper.ts:1 — Nothing ultimately consumes this binding: its only referrer is the re-export in JFKFiles/frontend/src/util/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in JFKFiles/frontend/src/util/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused module-local declaration 'cslPrefix' · ×1

Unused module-local declaration 'cslPrefix' GoogleAssistantConnector/GoogleAssistant/DirectLineToActionsOnGoogleLib/lib/mapper/ListCardMapper.js:4 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.

R7 · Dead Code · Unused module-local declaration 'BarProps' · ×1

Unused module-local declaration 'BarProps' JFKFiles/frontend/src/pages/search-page/components/page-bar/page-bar.component.tsx:12 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.

R7 · Dead Code · Unused private field 'informMessage' · ×1

Unused private field 'informMessage' JFKFiles/frontend/src/pages/search-page/search-page.container.tsx:170 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.

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

Not all async methods take a CancellationToken — Only 12/120 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/1 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 — 12 finding(s)

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

XML-doc coverage: SnipInsight Snip-Insights/SnipInsight/SnipInsight.csproj — SnipInsight: 28 % XML-doc coverage (406/1431).
XML-doc coverage: Speaker.Recorder VirtualStage/Speaker.Recorder/Speaker.Recorder/Speaker.Recorder.csproj — Speaker.Recorder: 1 % XML-doc coverage (4/350).
XML-doc coverage: Speaker.Recorder.UWP.Controls VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP.Controls/Speaker.Recorder.UWP.Controls.csproj — Speaker.Recorder.UWP.Controls: 4 % XML-doc coverage (1/25).
XML-doc coverage: Speaker.Recorder.UWP VirtualStage/Speaker.Recorder/Speaker.Recorder.UWP/Speaker.Recorder.UWP.csproj — Speaker.Recorder.UWP: 0 % XML-doc coverage (0/3).
XML-doc coverage: Sketch2Code.Core Sketch2Code/Sketch2Code.Core/Sketch2Code.Core.csproj — Sketch2Code.Core: 0 % XML-doc coverage (0/118).
XML-doc coverage: Sketch2Code.AI Sketch2Code/Sketch2Code.AI/Sketch2Code.AI.csproj — Sketch2Code.AI: 0 % XML-doc coverage (0/20).
XML-doc coverage: Sketch2Code.Api Sketch2Code/Sketch2Code.Api/Sketch2Code.Api.csproj — Sketch2Code.Api: 0 % XML-doc coverage (0/2).
XML-doc coverage: Sketch2Code.Web Sketch2Code/Sketch2Code.Web/Sketch2Code.Web.csproj — Sketch2Code.Web: 0 % XML-doc coverage (0/61).
XML-doc coverage: ChatBot BuildAnIntelligentBot/src/ChatBot/ChatBot.csproj — ChatBot: 17 % XML-doc coverage (20/117).
XML-doc coverage: JfkWebApiSkills JFKFiles/JfkWebApiSkills/JfkWebApiSkills/JfkWebApiSkills.csproj — JfkWebApiSkills: 0 % XML-doc coverage (0/70).
XML-doc coverage: CardsBot GoogleAssistantConnector/DemoBot/BotUsingCards/CardsBot.csproj — CardsBot: 69 % XML-doc coverage (11/16).

D10 · Test Quality · Mock framework · ×1

Mock framework: Moq — SnipInsight.Forms.Tests references Moq.

Appendix B — Reproduction & audit trail

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

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9c7133c7f12043868718ea0c4febf032/history.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9c7133c7f12043868718ea0c4febf032/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	36	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	nuget	—	nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan	0	—
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	28	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	59	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `BuildAnIntelligentBot/src/ChatBot/wwwroot/lib/botchat.js`, `JFKFiles/frontend/src/pages/search-page/components/graph/graph-view.business.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — 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	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a16809-1366-7c6b-889c-93c92e1db139 · 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 — 7 field(s) across 4 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 — 3 field(s)

OCRViewModel.emailButtonVisibility Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:220
OCRViewModel.EmailButtonVisibility Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:225
OCRViewModel.SendNewEmailCommand Snip-Insights/SnipInsight/AIServices/AIViewModels/OCRViewModel.cs:265

Name — 2 field(s)

ReservationData.FullName BuildAnIntelligentBot/src/ChatBot/Models/ReservationData.cs:46
ReservationData.FirstName BuildAnIntelligentBot/src/ChatBot/Models/ReservationData.cs:52

Address — 1 field(s)

LandmarkModel.PostalCode Snip-Insights/SnipInsight/AIServices/AIModels/EntitySearchModel.cs:32

Phone — 1 field(s)

LandmarkModel.Telephone Snip-Insights/SnipInsight/AIServices/AIModels/EntitySearchModel.cs:34

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — bounded-context dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 42% · Weak · gated by D18, X4, X5 ·

At a glance — Architecture · 72% · Adequate · gated by R9 ·

At a glance — Maturity · 53% · Adequate · gated by D34 ·

At a glance — Readiness · 16% · Critical · gated by R4, R6, P1, P3, P7 ·

At a glance — Security · 27% · Weak · gated by D29, D30, D31, D44, C2, S1 ·

At a glance — Accessibility · 39% · Weak · gated by AC4 ·

At a glance — Performance · 85% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Appendix C — Personal-data map

Downloadable artifacts