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

DEVids-VT/Insightify

Measured 22 October 2026, 00:40 UTC, at code version 7a89c22

Bus factor: not measured

Bus factor is not measured: No living knowledge left to concentrate.

CAI score 36out of 100 At risk Down 1 since the last survey

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

Event-Driven 100 Exemplary Performance 70 Adequate Architecture 67 Adequate Code Health 61 Adequate Maturity 46 Weak Security and Compliance 44 Weak Accessibility 36 Weak Production Readiness 26 Weak

A small codebase: 11,504 lines of product code in 27 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 26

Findings by how serious they are

234 critical 295 serious 211 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 00:40 UTC

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

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

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

101of 105 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
651of 740 findings point to an exact file and line, so you can open each one in the code. The other 89 concern the repository as a whole, such as missing documentation.
105dimensions across 8 lenses, read from 11,504 lines of product code in 27 projects.
Chapters

Executive summary

DEVids-VT/Insightify scores 36 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 26 and is rated Weak. Its Dependency Hygiene 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 7 Leaked secret finding(s) in REDACTED Scanning and to resolve the 4 Vulnerable finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 36 to about 44.

234 findings are critical: 74 in Dependency Vulnerabilities, 70 in Static Analysis (SAST), 21 in IaC & Container Security, 15 in Keyboard semantics, 11 in Forms & labels, 11 in Text alternatives, ten in Explicit Debt, seven in REDACTED Scanning, five in Page structure, four in Dependency Hygiene, three in Secrets (history) and three in Test isolation.

Watchdog couldn't measure Code Coverage, Documentation Quality and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 11,504 lines, which would take an estimated 0.1 person-years, around €14,000, to rebuild.

Code Health 61 Adequate, capped by Structured logging Architecture 67 Adequate, capped by Test isolation Maturity 46 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 26 Weak, capped by Dependency Hygiene, REDACTED Scanning, DR & Backup and Outbound HTTP resilience Security and Compliance 44 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities, IaC & Container Security, Supply-chain Provenance & Signing and Data Protection Event-Driven 100 ★ Exemplary Accessibility 36 Weak, capped by Text alternatives, Keyboard semantics and Visual & motion safety Performance 70 Adequate

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 26 · counts for 45%Accessibility 36 · counts for 25%Security and Compliance 44 · counts for 14%Maturity 46 · counts for 8%Code Health 61 · counts for 4%Architecture 67 · counts for 2%Performance 70 · counts for 1%Event-Driven 100 · counts for 1%

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

Code composition: what the lines of code are Most of the hand-written code is supporting code, such as wiring, settings and declarations, and business logic is 10% of it. That is normal for a service that mainly connects other systems or stores and fetches records, and worth a look if this product is meant to hold complex business rules.
Business logic 8%Supporting code 68%Tests 10%Generated by tools 15%
New since the last survey: 118 findings

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

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: 10 findings

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

  • Dependency Hygiene · Deprecated: AutoMapper.Extensions.Microsoft.DependencyInjection
  • Dependency Hygiene · Deprecated: xunit
  • Static Analysis (SAST) · Medium: REDACTED REDACTED
  • Static Analysis (SAST) · Medium: REDACTED src/Web/Insightify.MVC/Insightify.MVC/Controllers/AccountController.cs
  • Static Analysis (SAST) · Medium: REDACTED REDACTED
  • Static Analysis (SAST) · Medium: REDACTED REDACTED
  • Static Analysis (SAST) · Medium: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €14,000 · Estimate
Cost to rebuild€4,800 to €23,000, for 80 to 247 hours of work, about 0.1 person-years for one engineer
Difficulty of the problemVery high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 36. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 11,504 lines of product code

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

Top priorities

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

1
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (3).
Raises the score by about 8 points · Low effort · REDACTED Scanning
2
Resolve the 4 Vulnerable finding(s) in Dependency Hygiene.
Raises the score by about 7 points · Low effort · Dependency Hygiene
3
Resolve the 31 Outdated finding(s) in Dependency Hygiene — start with Insightify.Framework.csproj (9), REDACTED (3), REDACTED (3).
Raises the score by about 9 points · Medium effort · Dependency Hygiene

Diagnosis: what the measurements show together

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

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

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

arch FinancialDataApi FinancialDataApi MVC MVC FinancialBackgroundTasks FinancialBackgroundTasks Friendships Friendships IdentityAPI IdentityAPI Insightify.MVC Insightify.MVC NewsAPI NewsAPI NewsBackgroundTasks NewsBackgroundTasks NotificationsAPI NotificationsAPI Posts.Startup Posts.Startup ctx:Services Services Application · Infrastructure · Web Posts.Startup->ctx:Services SPA SPA Web.Gateway Web.Gateway __more__ +1 more contexts

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.

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

The table shows the 40 modules with the most connections; 146 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 Insighify.FinancialDataApi.Services.Contracts2 Insightify.Framework3 Insightify.Framework.Fetching.Interfaces4 Insightify.Framework.Messaging.Abstractions.Interfaces5 Insightify.Framework.MongoDb.Abstractions.Interfaces6 Insightify.Framework.Pagination.Abstractions7 Insightify.IdentityAPI.Controllers8 Insightify.MVC.Infrastructure.Mapping9 Insightify.Posts.Application.Common10 Insightify.Posts.Application.Common.Gateways11 Insightify.Posts.Application.Common.Mapping12 Insightify.Web.Gateway.Clients13 Insightify.Web.Gateway.Infrastructure.Mapping14 Insigghtify.Framework.Mongo15 Insighify.FinancialDataApi.Services16 Insightify.Framework.MongoDb.Abstractions17 Insightify.Framework.Swagger18 Insightify.MVC.Models.Posts19 Insightify.NewsBackgroundTasks.Services20 Insightify.NotificationsAPI.Services21 Insightify.Posts.Application.Posts22 Insightify.Posts.Application.Posts.Commands.Create23 Insightify.Posts.Application.Posts.Commands.Edit24 Insightify.Web.Gateway.Models25 Insightify.Web.Gateway.Models.FinancialData26 Insightify.MVC.Clients27 Insightify.Posts.Application.Posts.Queries.Comments28 Insightify.Posts.Application.Posts.Queries.Common29 Insightify.Posts.Application.Posts.Queries.Like30 Insightify.Web.Gateway.Services.FinancialData31 Insightify.Web.Gateway.Services.News32 Insightify.Web.Gateway.Services.Posts33 Insightify.MVC.Services.FinancialData34 Insightify.MVC.Services.News35 Insightify.MVC.Services.Posts36 Insightify.Posts.Application.Posts.Queries.Mine37 Insightify.Posts.Application.Posts.Queries.Search38 Insightify.Web.Gateway.Controllers39 Insightify.MVC.Controllers40 Insightify.Posts.Web.Features
1 Insighify.FinancialDataApi.Services.Contracts
2 Insightify.Framework
3 Insightify.Framework.Fetching.Interfaces
4 Insightify.Framework.Messaging.Abstractions.Interfaces
5 Insightify.Framework.MongoDb.Abstractions.Interfaces
6 Insightify.Framework.Pagination.Abstractions
7 Insightify.IdentityAPI.Controllers
8 Insightify.MVC.Infrastructure.Mapping
9 Insightify.Posts.Application.Common
10 Insightify.Posts.Application.Common.Gateways
11 Insightify.Posts.Application.Common.Mapping
12 Insightify.Web.Gateway.Clients
13 Insightify.Web.Gateway.Infrastructure.Mapping
14 Insigghtify.Framework.Mongo2
15 Insighify.FinancialDataApi.Services1
16 Insightify.Framework.MongoDb.Abstractions1
17 Insightify.Framework.Swagger1
18 Insightify.MVC.Models.Posts3
19 Insightify.NewsBackgroundTasks.Services1
20 Insightify.NotificationsAPI.Services3
21 Insightify.Posts.Application.Posts1
22 Insightify.Posts.Application.Posts.Commands.Create12
23 Insightify.Posts.Application.Posts.Commands.Edit11
24 Insightify.Web.Gateway.Models2
25 Insightify.Web.Gateway.Models.FinancialData22
26 Insightify.MVC.Clients12
27 Insightify.Posts.Application.Posts.Queries.Comments111
28 Insightify.Posts.Application.Posts.Queries.Common111
29 Insightify.Posts.Application.Posts.Queries.Like22
30 Insightify.Web.Gateway.Services.FinancialData14
31 Insightify.Web.Gateway.Services.News212
32 Insightify.Web.Gateway.Services.Posts214
33 Insightify.MVC.Services.FinancialData41
34 Insightify.MVC.Services.News21
35 Insightify.MVC.Services.Posts2102
36 Insightify.Posts.Application.Posts.Queries.Mine1113
37 Insightify.Posts.Application.Posts.Queries.Search1124
38 Insightify.Web.Gateway.Controllers11111
39 Insightify.MVC.Controllers2111
40 Insightify.Posts.Web.Features1311111
Uses a module listed above itPart of a loopThe module itself
1 Insighify.FinancialDataApi.Services.Contracts2 Insightify.Framework3 Insightify.Framework.Fetching.Interfaces4 Insightify.Framework.Messaging.Abstractions.Interfaces5 Insightify.Framework.MongoDb.Abstractions.Interfaces6 Insightify.Framework.Pagination.Abstractions7 Insightify.IdentityAPI.Controllers8 Insightify.MVC.Infrastructure.Mapping9 Insightify.Posts.Application.Common10 Insightify.Posts.Application.Common.Gateways11 Insightify.Posts.Application.Common.Mapping12 Insightify.Web.Gateway.Clients13 Insightify.Web.Gateway.Infrastructure.Mapping14 Insigghtify.Framework.Mongo15 Insighify.FinancialDataApi.Services16 Insightify.Framework.MongoDb.Abstractions17 Insightify.Framework.Swagger18 Insightify.MVC.Models.Posts19 Insightify.NewsBackgroundTasks.Services20 Insightify.NotificationsAPI.Services21 Insightify.Posts.Application.Posts22 Insightify.Posts.Application.Posts.Commands.Create23 Insightify.Posts.Application.Posts.Commands.Edit24 Insightify.Web.Gateway.Models25 Insightify.Web.Gateway.Models.FinancialData26 Insightify.MVC.Clients27 Insightify.Posts.Application.Posts.Queries.Comments28 Insightify.Posts.Application.Posts.Queries.Common29 Insightify.Posts.Application.Posts.Queries.Like30 Insightify.Web.Gateway.Services.FinancialData31 Insightify.Web.Gateway.Services.News32 Insightify.Web.Gateway.Services.Posts33 Insightify.MVC.Services.FinancialData34 Insightify.MVC.Services.News35 Insightify.MVC.Services.Posts36 Insightify.Posts.Application.Posts.Queries.Mine37 Insightify.Posts.Application.Posts.Queries.Search38 Insightify.Web.Gateway.Controllers39 Insightify.MVC.Controllers40 Insightify.Posts.Web.FeaturesInsighify.FinancialDataApi.Services.Contracts1Insightify.Framework2Insightify.Framework.Fetching.Interfaces3Insightify.Framework.Messaging.Abstractions.Interfaces4Insightify.Framework.MongoDb.Abstractions.Interfaces5Insightify.Framework.Pagination.Abstractions6Insightify.IdentityAPI.Controllers7Insightify.MVC.Infrastructure.Mapping8Insightify.Posts.Application.Common9Insightify.Posts.Application.Common.Gateways10Insightify.Posts.Application.Common.Mapping11Insightify.Web.Gateway.Clients12Insightify.Web.Gateway.Infrastructure.Mapping13Insigghtify.Framework.Mongo14Insighify.FinancialDataApi.Services15Insightify.Framework.MongoDb.Abstractions16Insightify.Framework.Swagger17Insightify.MVC.Models.Posts18Insightify.NewsBackgroundTasks.Services19Insightify.NotificationsAPI.Services20Insightify.Posts.Application.Posts21Insightify.Posts.Application.Posts.Commands.Create22Insightify.Posts.Application.Posts.Commands.Edit23Insightify.Web.Gateway.Models24Insightify.Web.Gateway.Models.FinancialData25Insightify.MVC.Clients26Insightify.Posts.Application.Posts.Queries.Comments27Insightify.Posts.Application.Posts.Queries.Common28Insightify.Posts.Application.Posts.Queries.Like29Insightify.Web.Gateway.Services.FinancialData30Insightify.Web.Gateway.Services.News31Insightify.Web.Gateway.Services.Posts32Insightify.MVC.Services.FinancialData33Insightify.MVC.Services.News34Insightify.MVC.Services.Posts35Insightify.Posts.Application.Posts.Queries.Mine36Insightify.Posts.Application.Posts.Queries.Search37Insightify.Web.Gateway.Controllers38Insightify.MVC.Controllers39Insightify.Posts.Web.Features4021113131121122212111111221421221441212102111311241111121111311111+146 more modules (most-connected shown)

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

The Good
D1 · .NET / C# Cyclomatic Complexity 10.0 D2 · .NET / C# Cognitive Complexity 10.0 D3 · .NET / C# God Classes 10.0 D4 · .NET / C# Code Duplication 9.2 D17 · .NET / C# Explicit Debt 7.4 D18 · .NET / C# Solution Shape 10.0 D39 · .NET / C# IL Efficiency 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.9 R1 · React / TS Type Safety 10.0 R10 · React / TS Code Duplication 10.0 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 8.2 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0 X5 · Repo Nullable reference types 8.1
The Bad
X2 · Repo Cancellation propagation 5.4 X23 · Repo Unguarded diagnostic materialisation 5.0
The Ugly
X20 · Repo Mistyped argument guard 3.5 X3 · Repo Exception handling 4.6 X4 · Repo Structured logging 3.9

At a glance — Architecture · 67% · Adequate · gated by AX8 ·

The Good
D5 · .NET / C# Coupling 9.7 D6 · .NET / C# Cohesion (LCOM4) 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 9.2 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9 AX9 · Repo CQS / query purity 10.0 R9 · React / TS Circular Imports 10.0
The Ugly
AX10 · Repo Code composition 4.1 AX8 · Repo Test isolation 2.5

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

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

At a glance — Readiness · 26% · Weak · gated by D12, D13, P5, P7 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D11 · .NET / C# Test Reliability 10.0 D14 · .NET / C# License Compliance 10.0 ED5 · Repo Idempotency 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.1 P8 · Repo Schema migrations 10.0 R5 · React / TS Dependency Freshness 8.6 R8 · React / TS Dependency Hygiene 8.5
The Bad
P10 · Repo Library API & versioning 6.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0 R6 · React / TS Tooling 6.7
The Ugly
D12 · .NET / C# Dependency Hygiene 0.0 D13 · .NET / C# REDACTED Scanning 0.0 P3 · Repo Security & performance tooling 4.0 P5 · Repo DR & Backup 0.0 P7 · Repo Outbound HTTP resilience 3.0 R4 · React / TS Test Coverage 4.6

At a glance — Security · 44% · Weak · gated by D29, D30, D31, D36, C1 ·

The Good
D28 · .NET / C# Secrets (history) 7.0 D43 · .NET / C# Malicious Dependencies 10.0 C2 · Repo Access Controls 8.0 C4 · Repo Data Retention 7.5 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
D44 · .NET / C# Platform End-of-Life 6.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 0.0 D30 · .NET / C# Dependency Vulnerabilities 0.0 D31 · .NET / C# IaC & Container Security 0.5 D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 3.0 S1 · Repo Web-Security Posture 4.0 X24 · Repo Document value interpolated into markup unescaped 4.5

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

The Good
ED1 · Repo Handler temporal coupling 10.0 ED2 · Repo Event/command shape 10.0

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

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

At a glance — Performance · 70% · Adequate ·

The Good
PF3 · Repo Async & latency hygiene 10.0
The Bad
PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection139High / Critical
A03:2025 — Software Supply Chain Failures125High / Critical
A02:2025 — Security Misconfiguration48High / Critical
A07:2025 — Authentication Failures11High / Critical

Roadmap

Begin by addressing the 31 outdated dependencies, prioritizing updates in the framework, identity API, and web gateway projects. Next, immediately remediate the 7 leaked secrets found in configuration files and container definitions, then resolve the 4 vulnerable dependencies. Follow this by cleaning up the 10 deprecated dependencies across the identity, background tasks, and application projects. Finally, establish a robust disaster recovery strategy by codifying backups and geo-recovery in infrastructure as code, while clearly documenting recovery time and point objectives.

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

Do thisHelpsEffortDimension
Resolve the 7 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (4), REDACTED (3).+8.4 ptsLowREDACTED Scanning
Resolve the 4 Vulnerable finding(s) in Dependency Hygiene.+6.9 ptsLowDependency Hygiene
Resolve the 31 Outdated finding(s) in Dependency Hygiene — start with Insightify.Framework.csproj (9), REDACTED (3), REDACTED (3).+8.5 ptsMediumDependency Hygiene
Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED, Insightify.Posts.Application.csproj.+6.6 ptsMediumDependency Hygiene
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.+4.1 ptsMediumDR & Backup
Resolve the 1 No ADRs found finding(s) in ADR Quality.+1.6 ptsLowADR Quality
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.5 ptsMediumKeyboard semantics
Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtensions.cs (8), Program.cs (7), CryptoCurrencyModel.cs (3).+1.8 ptsMediumKnowledge Freshness

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED0.4SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.0SlopIaC & Container Security: Critical IaC: REDACTED
REDACTED3.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.4SlopIaC & Container Security: High IaC: 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 — 234

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

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

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

Could not be resolved — 5

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. 101 of 105 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 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 — 105 dimensions across the health lenses
D1D2D3D4D5D6D9D10D11D12D13D14D15D17D18D20D21D24D26D27D28D29D30D31D34D35D36D39D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX5AX6AX8AX9C1C2C4ED1ED2ED5GD1IC1M1M2M3M4P1P10P2P3P4P5P6P7P8PF1PF2PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1610d-4d07-789e-859f-d891ad6bc475.

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.

  • D8 Code Coverage — 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. Coverage NOT MEASURED: the .NET half measured 10.7%; the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — src/Web/Angular.Client/insightify-client/ (karma) — a gap in the analyzer, not something this repository is missing. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • D10 Test Quality — 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 30 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 6 test source file(s) (.ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • 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. All 39 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 39 of the 301 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
  • 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 'REDACTED' with message: The target framework 'net7.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support po….
  • D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • 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; `src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/keys/is-signing-key-DFB413263DA58B495324B2F412144995.json`, `src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/keys/is-signing-key-97E3534C57C93904F8CDA42F4944C14A.json`, `src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/keys/is-signing-key-6E93B9EC163014A33B521D6C3BF50A1A.json`, `src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/keys/is-signing-key-3656C178E501EA8C77A34CD6E9E0B52A.json`, `src/Web/Insightify.SPA/Insightify.SPA/wwwroot/sample-data/weather.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • 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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — posts Error context canceled redis Error context canceled notifications Error context canceled rabbitmq Error context canceled sqlserver Error context canceled newsbgtasks Error context canceled identityserver Error context canceled gateway Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: redis Error context canceled newsbgtasks Error context canceled newsapi Error context canceled posts Error context canceled notifications Error context canceled financialapi Error context canceled mongo Error context canceled mvc Error context canceled sqlserver Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
  • 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. 75 further occurrence(s) are not listed individually; the score already reflects all 115.

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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • 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.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

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

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cognitive complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

D3 · God Classes10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

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

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

Members sharing a duplicated core (4 members, 50+ identical tokens)src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/News/NewsService.cs:26
Duplicated block (112 lines × 4)src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:250
Duplicated block (74 lines × 5)src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:7
Duplicated block (34 lines × 4)src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:184
Duplicated block (22 lines × 4)src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:124

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

What to do

  1. Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with NewsService.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Duplicated block (112 lines × 4) finding(s) in Code Duplication — start with CryptoCurrencyResponseModel.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (74 lines × 5) finding(s) in Code Duplication — start with CryptoCurrencyResponseModel.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling9.7 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

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

Off the main sequence: Insightify.Frameworksrc/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with Insightify.Framework.csproj. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 22 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

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

38 test methods: 38 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 8 `it`/`test` case(s) across 6 test file(s) declaring at least one beside 30 .NET test method(s); its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, 4 mock references across 30 tests. Measured on the C# suite only — at least 6 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.

Mock-dominated test: Delete_Should_Delete_Article_When_Article_Foundsrc/Services/Insightify.NewsAPI/Insightify.NewsAPI.Tests/NewsServiceTests.cs:80
Mock framework: Moq · ×4

✓ On the Gold path — maintain.

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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

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

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

72 outdated, 4 vulnerable, 4 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 17 outdated of 22 package(s) across 1 lockfile(s).

Vulnerable: Duende.IdentityServer · ×4
Deprecated: Duende.IdentityServer · ×10REDACTED:16
Outdated: Microsoft.AspNetCore.OpenApi · ×31REDACTED:36
Outdated (npm): @angular/animations · ×9src/Web/Angular.Client/insightify-client/package.json:13
Deprecated: @npmcli/move-fileREDACTED:2887

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

What to do

  1. Resolve the 31 Outdated finding(s) in Dependency Hygiene — start with Insightify.Framework.csproj (9), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (31 recommendation-level).
  2. Resolve the 4 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2), REDACTED, Insightify.Posts.Application.csproj. — One of this dimension's main actionable groups (10 warning-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

3 secret(s) detected.

REDACTED

What to do

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 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.

D17 · Explicit Debt7.4 / 10Adequategated by 10 critical findings✓ Tool-verified

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

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

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

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

WriteOnlyPrivateField · ×9src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Services/CryptoDataService.cs:13
EmptyCatchBlocksrc/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:35
CoverageExclusion · ×12src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Extensions/ServiceCollectionExtensions.cs:13
CommentedOutCode · ×2src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Middlewares/ExceptionHandlingMiddleware.cs:36

What to do

  1. Resolve the 9 WriteOnlyPrivateField finding(s) in Explicit Debt — start with CryptoCurrencyJob.cs (2), MarketChartsJob.cs (2), CryptoDataService.cs. — One of this dimension's main actionable groups (9 issue-level).
  2. Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with AccountSettingsService.cs. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 12 CoverageExclusion finding(s) in Explicit Debt — start with Program.cs (5), ServiceCollectionExtensions.cs (4), DatabaseMiddleware.cs (2). — One of this dimension's main actionable groups (12 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

27 projects, 390 source files, 12201 hand-written lines of code (10827 production / 1374 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 2186 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 17 inter-project edges. Measured across 4 solutions loaded as one workspace: `Insightify.sln`, `src/Web/Insightify.MVC/Insightify.MVC.sln`, `src/Services/Insightify.NewsAPI/Insightify.NewsAPI.sln`, `src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks.sln`.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

1 naming inconsistencies across 200 sampled symbols.

Spelling error: 'Opperations' vs 'Operations'. The type name contains a typo in the word 'Operations'.

✓ On the Gold path — maintain.

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

D24 · Comment ValueExemplary◐ Sampled · advisory

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

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

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

32 valuable / 0 redundant across 90 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

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

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

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

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

0 of 27 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

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

97 % of calls cross a namespace and 7 % go through an interface, but 99 % 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.

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)0.0 / 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.0 / 10 · rule-coverage 100% · ceiling Documented

139 finding(s): 0 critical, 70 high, 69 medium, 0 low. 49 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 18 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (18 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. No action in Static Analysis (SAST) — all 49 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (49 issue-level, 0 of them charged here).

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

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

110 finding(s): 9 critical, 65 high, 27 medium, 9 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 64 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (48), REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (64 issue-level).
  2. Resolve the 9 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
  3. 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.

D31 · IaC & Container Security0.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 0.5 / 10 · rule-coverage 100% · ceiling Documented

48 finding(s): 1 critical, 20 high, 20 medium, 7 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 20 High IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (9). — One of this dimension's main actionable groups (20 issue-level).
  2. Resolve the 20 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (18), REDACTED (2). — One of this dimension's main actionable groups (20 warning-level).
  3. Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

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

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

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

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

39 of 39 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs. Counted over 39 of the 301 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×39src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs:1
Dormant codebase

What to do

  1. Resolve the 39 Orphaned file finding(s) in Knowledge Freshness — start with ServiceCollectionExtensions.cs (8), Program.cs (7), CryptoCurrencyModel.cs (3). — One of this dimension's main actionable groups (39 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 10 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified

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

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

0 of 859 first-party methods have an oversized IL body.

✓ On the Gold path — maintain.

Detailed fixes: d39_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

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

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

What to do

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

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives4.0 / 10Weak✓ 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. (×11) — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.cshtml:24, REDACTED:6, src/Web/Insightify.MVC/Insightify.MVC/wwwroot/js/posts/dynamic_page_display.js:43, …

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels5.0 / 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.

  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×7) — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.cshtml:26, src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:44, src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:45, …
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:19, src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:53
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:20
  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:11

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.4 / 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.

  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×5) — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.cshtml:57, src/Web/Insightify.MVC/Insightify.MVC/Views/Home/Index.cshtml:39, src/Web/Insightify.SPA/Insightify.SPA/Pages/Index.razor:21, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/Web/Insightify.MVC/Insightify.MVC/Views/Shared/_HomeLayout.cshtml:2
  • A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet). (×4) — src/Web/Insightify.SPA/Insightify.SPA/Pages/Authentication.razor:3, src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:2, src/Web/Insightify.SPA/Insightify.SPA/Pages/Dashboard.razor:5, …
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — src/Web/Insightify.SPA/Insightify.SPA/wwwroot/index.html:6

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard 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".

  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×24) — REDACTED:41, REDACTED:42, src/Web/Insightify.MVC/Insightify.MVC/Views/Home/Index.cshtml:48, …
  • The repo's own CSS styles .report-btn with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:23
  • The repo's own CSS styles .fa-regular with `cursor: pointer`, so this <i> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×5) — src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:24, src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:44, src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:45, …
  • The repo's own CSS styles .follow-bth with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:84
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:11
  • The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×7) — src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:14, src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:19, src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:24, …

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

  • `.account-menu:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor.css:21
  • `.top-row .top-row-left .top-row-item:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.SPA/Insightify.SPA/Shared/MainLayout.razor.css:30
  • `.nav-item ::deep a:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor.css:48
  • `.links .link-item:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor.css:125, src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/crypto.css:142
  • `.post-container .post-header .post-header-buttons .follow-btn` sets color: white on background-color: #C864F7 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/create-post.css:209
  • `.posts-container .sections-container .section-posts .post-container .post-header .post-header-buttons .follow-btn` sets color: white on background-color: #C864F7 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/feed.css:90
  • `.direct-message-item:hover` sets color: rgb(121, 120, 120) on background-color: #f0f0f0 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/layout.css:151
  • `body` sets color: #D1D5DB on background-color: white — 1.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/site.css:10
  • `.post-container-main .post-content-container .post-content-data .post-hashtags .hashtag` sets color: white on background-color: #ba46d7 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/view-post-page.css:128
  • `button` sets color: white on background-color: #808080 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Web/Angular.Client/insightify-client/src/app/identity/identity.component.css:1
  • `.btn-primary` sets color: white on background-color: #b649f3 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/wwwroot/css/account.css:51
  • `.bubbly-button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:9, src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:15
  • `.bubbly-button` moves (`transition: transform ease-in 0.1s, box-shadow ease-in 0.25s`) 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. (×2) — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:6, src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:12
  • `.bubbly-button.animate:before` moves (`animation: topBubbles ease-in-out 0.75s forwards`) 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. (×2) — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:41, src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:71
  • `.bubbly-button.animate:after` moves (`animation: bottomBubbles ease-in-out 0.75s forwards`) 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. (×2) — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:45, src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:75
  • `.notification-popup` moves (`animation: fadeIn 0.5s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/layout.css:386
  • `.loading-bar-container-img-gray` moves (`animation: breathe 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/site.css:20

What to do

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

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

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

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

  • No accessibility enforcement found — no a11y linter (@angular-eslint/eslint-plugin-template (a11y rules)) 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 42 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 @angular-eslint/eslint-plugin-template (a11y rules), 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.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

AX10 · Code composition4.1 / 10Weak✓ 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.
AX2 · Stateful singletons10.0 / 10Exemplary✓ 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.

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.

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

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

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

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

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

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

  • `IRepository<T>` declares 17 members under just 15 distinct name(s): `InsertAsync`, `InsertAsync`, `UpdateAsync`, `DeleteByIdAsync`, `DeleteAsync`, `DeleteAsync`, `DeleteOneAsync`, `DeleteManyAsync`, `RestoreAsync`, `RestoreByIdAsync`, `CountAsync`, `ExistsAsync`, `GetByIdAsync`, `GetAllAsync`, `GetPagedListAsync`, `GetFirstOrDefaultAsync`, `GetSingleOrDefaultAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/Common/Insightify.Framework/Mongo/Insightify.Framework.MongoDb.Abstractions/Interfaces/IRepository.cs:8

What to do

  • Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
AX8 · Test isolation2.5 / 10Weak✓ 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.

  • `Insightify.Posts.Application` (production) references the test project `Insightify.Posts.Domain`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — src/Services/Insightify.Posts/Insightify.Posts.Application/Insightify.Posts.Application.csproj:20
  • `Insightify.Posts.Infrastructure` (production) references the test project `Insightify.Posts.Domain`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — REDACTED:23
  • `Insightify.Posts.Startup` (production) references the test project `Insightify.Posts.Domain`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — src/Services/Insightify.Posts/Insightify.Posts.Startup/Insightify.Posts.Startup.csproj:21

What to do

  • Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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

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

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

C1 · Data Protection3.0 / 10Weak✓ Tool-verified

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

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

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

What to do

  • Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls8.0 / 10Strong✓ Tool-verified

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

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

  • [AllowAnonymous] (12) outweighs [Authorize] (6) — review whether the open surface is intended.

What to do

  • Review the [AllowAnonymous] surface — keep anonymous endpoints deliberate and documented so the open surface stays intentional.
C4 · Data Retention7.5 / 10Strong✓ Tool-verified

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

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

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
ED1 · Handler temporal coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

ED5 · Idempotency10.0 / 10Exemplary◐ Sampled · advisory

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

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

IC1 · Incompleteness & stubs8.9 / 10Strong✓ Tool-verified

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

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

  • `GetPosts` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Posts/Repositories/PostRepository.cs:108
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×4) — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Middlewares/ExceptionHandlingMiddleware.cs:42, src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Program.cs:52, src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Program.cs:25, …

What to do

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

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

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add a README to the 26 of 26 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

M4 · Documentation accuracy8.0 / 10Strong◐ Sampled · advisory

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

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

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

What to do

  • Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

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

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

  • 48/48 types (100%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.

What to do

  • Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability7.1 / 10Strong✓ Tool-verified

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

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

  • Only 14/20 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 20, 9 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

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.
  • Add OpenTelemetry tracing/metrics (ActivitySource / AddMetrics) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling4.0 / 10Weak✓ 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.

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

  • Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.

What to do

  • Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

  • A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

What to do

  • Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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

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

  • `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/Common/Insightify.Framework/Core/Insightify.Framework/CoreServicesBuilder.cs:16
  • `new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` 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). — src/Web/Insightify.SPA/Insightify.SPA/Program.cs:13

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.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

What to do

  • Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF2 · Allocation hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.

What to do

  • On hot paths, prefer Span<T>/ReadOnlySpan<T>, ArrayPool<T>, stackalloc and ValueTask to cut the allocations those paths would otherwise make.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

R1 · Type Safety10.0 / 10Exemplary✓ 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.

R10 · Code Duplication10.0 / 10Exemplary✓ 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.

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.

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.

R4 · Test Coverage4.6 / 10Weak✓ 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.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×7) — src/Web/Angular.Client/insightify-client/src/app/app.module.ts:1, src/Web/Angular.Client/insightify-client/src/app/news/news.module.ts:1, src/Web/Angular.Client/insightify-client/src/app/notifications/notification/notification.module.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.6 / 10Strong✓ 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.
R6 · Tooling6.7 / 10Adequate✓ 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 eslint as package.json scripts and run them in CI.
R7 · Dead Code8.2 / 10Strong✓ 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.

  • Unreachable from the 1 application, 0 tooling and 6 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 (1 application, 0 tooling, 6 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 — src/Web/Angular.Client/insightify-client/src/app/notifications/notification/notification.module.ts

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene8.5 / 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.

  • Declared in src/Web/Angular.Client/insightify-client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ 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.

S1 · Web-Security Posture4.0 / 10Weak✓ Tool-verified

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

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

  • `https://code.jquery.com/jquery-3.6.0.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. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 15 such include(s) across the repository's markup. — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.cshtml:71
  • `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path. — src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Extensions/ServiceCollectionExtensions.cs:49
  • `ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent. — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Extensions/ServiceCollectionExtensions.cs:68
  • 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. (×10) — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Program.cs:21, src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Program.cs:16, src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Program.cs:12, …

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
  • Set RequireHttpsMetadata = true in prod (or pin MetadataAddress to a localhost URL the API can hit directly).
  • Re-enable token validation — `ValidateAudience` is set to `false`. If it was switched off because the expected value was wrong or absent, supply that value instead (`ValidAudiences`/`ValidIssuers`, or `IssuerSigningKeys`/`IssuerSigningKeyResolver` for the signature) rather than skipping the check: a disabled check accepts every token, not just the one that was failing.
  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard3.5 / 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 34 rejects `ApiName` and line 36 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ApiName)` is true of a value that is NOT null: it is satisfied by an EMPTY `ApiName`, and on that path `ApiName` 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. — src/Common/Insightify.Framework/Core/Insightify.Framework/Swagger/Settings/SwaggerSettings.cs:36
  • The guard on line 39 rejects `JsonRoute` and line 41 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(JsonRoute)` is true of a value that is NOT null: it is satisfied by an EMPTY `JsonRoute`, and on that path `JsonRoute` 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. — src/Common/Insightify.Framework/Core/Insightify.Framework/Swagger/Settings/SwaggerSettings.cs:41
  • The guard on line 44 rejects `UiEndpoint` and line 46 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(UiEndpoint)` is true of a value that is NOT null: it is satisfied by an EMPTY `UiEndpoint`, and on that path `UiEndpoint` 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. — src/Common/Insightify.Framework/Core/Insightify.Framework/Swagger/Settings/SwaggerSettings.cs:46

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.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X23 · Unguarded diagnostic materialisation5.0 / 10Adequate✓ Tool-verified

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

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

  • `LogDebug` at line 64 is called with an argument built by `string.Join(", ", entities.Select(e => e.Id))` (line 64), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:64
  • `LogDebug` at line 178 is called with an argument built by `string.Join(", ", entities.Select(e => e.Id))` (line 178), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:178

What to do

  • Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.
X24 · Document value interpolated into markup unescaped4.5 / 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.

  • `jsonDataPrices` 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. — src/Web/Insightify.MVC/Insightify.MVC/Views/FinancialData/Dashboard.cshtml:156
  • `jsonDataTotalVolumes` 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. — src/Web/Insightify.MVC/Insightify.MVC/Views/FinancialData/Dashboard.cshtml:157
  • `jsonDataMarket` 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. — src/Web/Insightify.MVC/Insightify.MVC/Views/FinancialData/Dashboard.cshtml:158

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X3 · Exception handling4.6 / 10Weak✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:35
  • `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. — src/Services/Insightify.Notifications/Insightify.Notifications/Services/NotificationService.cs:35
  • `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack. — src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Jobs/CryptoCurrencyJob.cs:46

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

  • Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×17) — src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Services/NewsReadService.cs:42, src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Services/NewsService.cs:37, src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Services/NewsService.cs:51, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types8.1 / 10Strong✓ 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.

  • 22/23 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.
  • ~2.0 `!` suppressions per 1k syntax nodes — 130 suppression(s) across the 66283 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

WCAG coverage — what static analysis assessed

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

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health61%Adequate — gated by X4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture67%Adequate — gated by AX8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity46%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness26%Weak — gated by D12, D13, P5, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security44%Weak — gated by D29, D30, D31, D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event-Driven100%ExemplaryStrongest area.
Accessibility36%Weak — gated by AC1, AC4, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance70%AdequateAcceptable, with room to improve.
Unscored — 2 check(s) recorded observations but carry no score

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

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

  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — posts Error context canceled redis Error context canceled notifications Error context canceled rabbitmq Error context canceled sqlserver Error context canceled newsbgtasks Error context canceled identityserver Error context canceled gateway Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: redis Error context canceled newsbgtasks Error context canceled newsapi Error context canceled posts Error context canceled notifications Error context canceled financialapi Error context canceled mongo Error context canceled mvc Error context canceled sqlserver Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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.
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D19 Documentation Quality — LLM evaluation failed
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — small single-context codebase (10,827 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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"]`.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 aggregate-constrained repository/repositories (IRepository<T> where T : IAggregateRoot))
  • ED3 Event naming — no domain or integration events detected — event-naming check not applicable
  • ED4 Outbox / dual-write — no persistence writes or publishes observed in handlers — atomicity not assessable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • 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
  • 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.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X8 JS interop contract — 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 — 234 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×64
  • 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
  • + 39 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 24 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×20
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×14
  • Clickable element isn't keyboard-operable src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:23 — The repo's own CSS styles .report-btn with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:24 — The repo's own CSS styles .fa-regular with `cursor: pointer`, so this <i> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:44 — The repo's own CSS styles .fa-regular with `cursor: pointer`, so this <i> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:45 — The repo's own CSS styles .fa-regular with `cursor: pointer`, so this <i> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:47 — The repo's own CSS styles .fa-regular with `cursor: pointer`, so this <i> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:84 — The repo's own CSS styles .follow-bth with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:13 — The repo's own CSS styles .fa-regular with `cursor: pointer`, so this <i> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:14 — The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:19 — The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:24 — The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:29 — The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:34 — The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:82 — The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:87 — The repo's own CSS styles .hover with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AC1 · Text alternatives · <img> without a text alternative · ×11
  • <img> without a text alternative src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.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 REDACTED:6 — 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 src/Web/Insightify.MVC/Insightify.MVC/wwwroot/js/posts/dynamic_page_display.js:43 — 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 src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor: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 src/Web/Insightify.SPA/Insightify.SPA/Pages/Dashboard.razor:10 — 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 src/Web/Insightify.SPA/Insightify.SPA/Pages/Dashboard.razor:25 — 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 src/Web/Insightify.SPA/Insightify.SPA/Pages/Dashboard.razor: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 src/Web/Insightify.SPA/Insightify.SPA/Pages/Dashboard.razor:55 — 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 src/Web/Insightify.SPA/Insightify.SPA/Pages/News.razor:13 — 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 src/Web/Insightify.SPA/Insightify.SPA/Pages/News.razor: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 src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:9 — 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 · WriteOnlyPrivateField · ×9
  • WriteOnlyPrivateField src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Services/CryptoDataService.cs:13 — private ILogger _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Jobs/CryptoCurrencyJob.cs:17 — private ILogger _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Jobs/MarketChartsJob.cs:22 — private ILogger _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Jobs/CryptoCurrencyJob.cs:18 — private IMessagePublisher _publisher — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Jobs/MarketChartsJob.cs:23 — private IMessagePublisher _publisher — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Controllers/AccountController.cs:25 — private IEventService _events — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Services/Insightify.Notifications/Insightify.Notifications/Consumer/EventConsumer.cs:19 — private IValidator<Notification> _validator — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField src/Services/Insightify.Notifications/Insightify.Notifications/Services/NotificationService.cs:15 — private IValidator<Notification> _validator — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField REDACTED:11 — private ILogger<HomeController> _logger — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D30 · Dependency Vulnerabilities · Critical CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Link with no accessible name · ×7
  • Link with no accessible name src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.cshtml:26 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:44 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:45 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:46 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:47 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Web/Insightify.MVC/Insightify.MVC/Views/Shared/_HeaderPartialView.cshtml:4 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name src/Web/Insightify.MVC/Insightify.MVC/Views/Shared/_HeaderPartialView.cshtml:9 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
D13 · REDACTED Scanning · Leaked secret · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Routed page without a <PageTitle> · ×4
  • Routed page without a <PageTitle> src/Web/Insightify.SPA/Insightify.SPA/Pages/Authentication.razor:3 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
  • Routed page without a <PageTitle> src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:2 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
  • Routed page without a <PageTitle> src/Web/Insightify.SPA/Insightify.SPA/Pages/Dashboard.razor:5 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
  • Routed page without a <PageTitle> src/Web/Insightify.SPA/Insightify.SPA/Pages/Index.razor:6 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
D12 · Dependency Hygiene · Vulnerable · ×4
  • Vulnerable: Duende.IdentityServer — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: MailKit — REDACTED — Moderate severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: AutoMapper — REDACTED — High severity. https://github.com/advisories/[GHSA redacted]
  • Vulnerable: Refit — REDACTED — Critical severity. https://github.com/advisories/[GHSA redacted]
AX8 · Test isolation · Production project references a test project · ×3
  • Production project references a test project: Insightify.Posts.Application → Insightify.Posts.Domain src/Services/Insightify.Posts/Insightify.Posts.Application/Insightify.Posts.Application.csproj:20 — `Insightify.Posts.Application` (production) references the test project `Insightify.Posts.Domain`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: Insightify.Posts.Infrastructure → Insightify.Posts.Domain REDACTED:23 — `Insightify.Posts.Infrastructure` (production) references the test project `Insightify.Posts.Domain`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: Insightify.Posts.Startup → Insightify.Posts.Domain src/Services/Insightify.Posts/Insightify.Posts.Startup/Insightify.Posts.Startup.csproj:21 — `Insightify.Posts.Startup` (production) references the test project `Insightify.Posts.Domain`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
AC2 · Forms & labels · <textarea> without a programmatic label · ×2
  • <textarea> without a programmatic label src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:20 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <textarea> without a programmatic label src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:53 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×1
  • <input> without a programmatic label src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:19 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC2 · Forms & labels · <button> with no accessible text · ×1
  • <button> with no accessible text src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:11 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC3 · Page structure · Viewport restricts zoom · ×1
  • Viewport restricts zoom src/Web/Insightify.SPA/Insightify.SPA/wwwroot/index.html:6 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×1
  • Click handler on a non-interactive <div> src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor:11 — 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 · EmptyCatchBlock · ×1
  • EmptyCatchBlock src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:35 — 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.
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
D31 · IaC & Container Security · Critical IaC · ×1
  • REDACTED
Serious — 295 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • 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: GetCryptoCurrency REDACTED:17 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetMarketChart REDACTED:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAllCurrencies REDACTED:43 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendFriendRequest REDACTED:20 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: AcceptFriendRequest REDACTED:29 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RejectFriendRequest REDACTED:37 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Unfriend REDACTED:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetRequests REDACTED:54 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAllRequests REDACTED:62 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetFriendships REDACTED:70 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetAllFriendships REDACTED:78 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Register src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Controllers/AccountController.cs:154 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: EditProfile REDACTED:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Profile REDACTED:33 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendEmailAsync src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/EmailSending/MailSender.cs:16 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: MigrateDatabase src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Middleware/DatabaseMiddleware.cs:13 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: EditProfile src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UploadToImgur src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:72 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetNewsArticle REDACTED:21 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetArticles REDACTED:28 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetNotification src/Services/Insightify.Notifications/Insightify.Notifications/Controllers/NotificationController.cs:22 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetNotifications src/Services/Insightify.Notifications/Insightify.Notifications/Controllers/NotificationController.cs:30 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SendNotificaiton src/Services/Insightify.Notifications/Insightify.Notifications/Services/NotificationService.cs:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: MigrateDatabase src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Middlewares/DatabaseMiddleware.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Send src/Services/Insightify.Posts/Insightify.Posts.Web/ApiController.cs:28 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 14 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×26
  • 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
  • + 1 more in this group — see findings.md.
AC4 · Keyboard semantics · Anchor without href · ×24
  • Anchor without href REDACTED:41 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href REDACTED:42 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Home/Index.cshtml:48 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Home/Index.cshtml:50 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:8 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:11 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:14 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:22 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/Create.cshtml:23 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/Views/Posts/ViewPost.cshtml:56 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/wwwroot/js/posts/dynamic_page_display.js:52 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.MVC/Insightify.MVC/wwwroot/js/posts/dynamic_page_display.js:53 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:28 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:29 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:30 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:31 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:36 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor:37 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:8 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:13 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:16 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:17 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:18 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor:19 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D31 · IaC & Container Security · Medium IaC · ×20
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · CoverageExclusion · ×12
  • CoverageExclusion src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Extensions/ServiceCollectionExtensions.cs:13 — class ServiceCollectionExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Extensions/ServiceCollectionExtensions.cs:9 — class ServiceCollectionExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Extensions/ServiceCollectionExtensions.cs:6 — class ServiceCollectionExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Extensions/ServiceCollectionExtensions.cs:12 — class ServiceCollectionExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Program.cs:98 — class Program — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Program.cs:93 — class Program — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Program.cs:102 — class Program — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.Posts/Insightify.Posts.Startup/Program.cs:57 — class Program — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Web/Insightify.MVC/Insightify.MVC/Program.cs:72 — class Program — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Extensions/ProgramExtensions.cs:16 — class ProgramExtensions — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Middleware/DatabaseMiddleware.cs:10 — class DatabaseMiddleware — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
  • CoverageExclusion src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Middlewares/DatabaseMiddleware.cs:11 — class DatabaseMiddleware — this shipped code is lifted out of the coverage measurement, so it is not that the code is reported as untested: it is not reported at all. The excluded lines leave the denominator, which means the percentage the team publishes goes UP when code stops being covered, and the gap is invisible in the artefact that would otherwise disclose it. Nothing here is written by a compiler or a build — the attribute is only ever typed by an author — so it is a standing decision, and the only record of it is this line. Test what it covers and delete the attribute; where the code genuinely cannot be exercised (a debugger display, a platform branch this build cannot reach), narrow the exclusion to the smallest declaration that is really untestable rather than the type around it, so members added later are not silently excluded too. If it is correct as it stands, say why — in the attribute's own Justification, or in a comment above it: that is what turns it from unexplained debt into a recorded decision, and it clears this row.
D12 · Dependency Hygiene · Deprecated · ×10
  • Deprecated: Duende.IdentityServer REDACTED:16 — REDACTED — Legacy
  • Deprecated: Duende.IdentityServer.AspNetIdentity REDACTED:17 — Duende.IdentityServer.AspNetIdentity 6.3.3 — Legacy
  • Deprecated: AutoMapper.Extensions.Microsoft.DependencyInjection REDACTED:21 — AutoMapper.Extensions.Microsoft.DependencyInjection 12.0.1 — Legacy — the publisher's replacement is `AutoMapper` >= 13.0.0; migrate the reference to it.
  • Deprecated: AutoMapper.Extensions.Microsoft.DependencyInjection src/Services/Insightify.Posts/Insightify.Posts.Application/Insightify.Posts.Application.csproj:11 — AutoMapper.Extensions.Microsoft.DependencyInjection 12.0.1 — Legacy — the publisher's replacement is `AutoMapper` >= 13.0.0; migrate the reference to it.
  • Deprecated: AutoMapper.Extensions.Microsoft.DependencyInjection src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:19 — AutoMapper.Extensions.Microsoft.DependencyInjection 12.0.1 — Legacy — the publisher's replacement is `AutoMapper` >= 13.0.0; migrate the reference to it.
  • Deprecated: xunit REDACTED:15 — xunit 2.4.2 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit REDACTED:18 — xunit 2.5.0 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit src/Common/Insightify.Framework/Tests/Insightify.Framework.Tests/Insightify.Framework.Tests.csproj:16 — xunit 2.5.0 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit src/Services/Insightify.NewsAPI/Insightify.NewsAPI.Tests/Insightify.NewsAPI.Tests.csproj:16 — xunit 2.4.2 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: @aspnet/signalr src/Web/Angular.Client/insightify-client/package.json:21 — @aspnet/signalr 1.0.27, declared in src/Web/Angular.Client/insightify-client/package.json, is marked deprecated by its publisher: "This package is no longer supported. Consider using @microsoft/signalr.". Replace it with the package or version that message names, or record why this one must stay.
D36 · Supply-chain Provenance & Signing REDACTED · ×10
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×8
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:6 — `.bubbly-button` moves (`transition: transform ease-in 0.1s, box-shadow ease-in 0.25s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:41 — `.bubbly-button.animate:before` moves (`animation: topBubbles ease-in-out 0.75s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:45 — `.bubbly-button.animate:after` moves (`animation: bottomBubbles ease-in-out 0.75s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:71 — `.bubbly-button.animate:before` moves (`animation: topBubbles ease-in-out 0.75s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:75 — `.bubbly-button.animate:after` moves (`animation: bottomBubbles ease-in-out 0.75s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:12 — `.bubbly-button` moves (`transition: transform ease-in 0.1s, box-shadow ease-in 0.25s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/layout.css:386 — `.notification-popup` moves (`animation: fadeIn 0.5s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/site.css:20 — `.loading-bar-container-img-gray` moves (`animation: breathe 2s 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.
R4 · Test Coverage · No test reaches this file · ×7
  • No test reaches this file src/Web/Angular.Client/insightify-client/src/app/app.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/Web/Angular.Client/insightify-client/src/app/news/news.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/Web/Angular.Client/insightify-client/src/app/notifications/notification/notification.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/Web/Angular.Client/insightify-client/src/app/news/news-routing.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/Web/Angular.Client/insightify-client/src/app/app-routing.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/Web/Angular.Client/insightify-client/src/app/shared/components/header/header.component.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file src/Web/Angular.Client/insightify-client/src/main.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.1 · ×5
  • Low contrast colour pair in CSS (3.1:1) src/Web/Insightify.SPA/Insightify.SPA/Shared/LoginDisplay.razor.css:21 — `.account-menu:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) src/Web/Insightify.SPA/Insightify.SPA/Shared/MainLayout.razor.css:30 — `.top-row .top-row-left .top-row-item:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) src/Web/Insightify.SPA/Insightify.SPA/Shared/NavMenu.razor.css:48 — `.nav-item ::deep a:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) src/Web/Insightify.SPA/Insightify.SPA/Pages/Crypto.razor.css:125 — `.links .link-item:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/crypto.css:142 — `.links .link-item:hover` sets color: #ad5adc on background-color: #ecdff5 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×3
  • Argument guard throws the exception its own condition disproves src/Common/Insightify.Framework/Core/Insightify.Framework/Swagger/Settings/SwaggerSettings.cs:36 — The guard on line 34 rejects `ApiName` and line 36 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(ApiName)` is true of a value that is NOT null: it is satisfied by an EMPTY `ApiName`, and on that path `ApiName` 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 src/Common/Insightify.Framework/Core/Insightify.Framework/Swagger/Settings/SwaggerSettings.cs:41 — The guard on line 39 rejects `JsonRoute` and line 41 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(JsonRoute)` is true of a value that is NOT null: it is satisfied by an EMPTY `JsonRoute`, and on that path `JsonRoute` 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 src/Common/Insightify.Framework/Core/Insightify.Framework/Swagger/Settings/SwaggerSettings.cs:46 — The guard on line 44 rejects `UiEndpoint` and line 46 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(UiEndpoint)` is true of a value that is NOT null: it is satisfied by an EMPTY `UiEndpoint`, and on that path `UiEndpoint` 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.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×3
  • Untrusted text written into markup unescaped src/Web/Insightify.MVC/Insightify.MVC/Views/FinancialData/Dashboard.cshtml:156 — `jsonDataPrices` 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 src/Web/Insightify.MVC/Insightify.MVC/Views/FinancialData/Dashboard.cshtml:157 — `jsonDataTotalVolumes` 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 src/Web/Insightify.MVC/Insightify.MVC/Views/FinancialData/Dashboard.cshtml:158 — `jsonDataMarket` 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.
AC3 · Page structure · Heading level jumps from h3 to h6 · ×2
  • Heading level jumps from h3 to h6 src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.cshtml:57 — 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 h6 src/Web/Insightify.MVC/Insightify.MVC/Views/Home/Index.cshtml:39 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Heading level jumps from h2 to h4 · ×2
  • Heading level jumps from h2 to h4 src/Web/Insightify.SPA/Insightify.SPA/Pages/Index.razor:21 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h4 src/Web/Insightify.SPA/Insightify.SPA/Pages/News.razor:36 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.2 · ×2
  • Low contrast colour pair in CSS (3.2:1) src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/create-post.css:209 — `.post-container .post-header .post-header-buttons .follow-btn` sets color: white on background-color: #C864F7 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.2:1) src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/feed.css:90 — `.posts-container .sections-container .section-posts .post-container .post-header .post-header-buttons .follow-btn` sets color: white on background-color: #C864F7 — 3.2: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.9 · ×2
  • Low contrast colour pair in CSS (3.9:1) src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/layout.css:151 — `.direct-message-item:hover` sets color: rgb(121, 120, 120) on background-color: #f0f0f0 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.9:1) src/Web/Angular.Client/insightify-client/src/app/identity/identity.component.css:1 — `button` sets color: white on background-color: #808080 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×2
  • Focus outline removed in CSS without a :focus replacement src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.css:9 — `.bubbly-button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/btn-animation.scss:15 — `.bubbly-button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
D17 · Explicit Debt · CommentedOutCode · ×2
  • CommentedOutCode src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Middlewares/ExceptionHandlingMiddleware.cs:36 — 7 consecutive commented-code lines
  • CommentedOutCode src/Services/Insightify.Notifications/Insightify.Notifications/Validators/NotificationValidator.cs:11 — 10 consecutive commented-code lines
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2
  • Outbound HTTP without resilience src/Common/Insightify.Framework/Core/Insightify.Framework/CoreServicesBuilder.cs:16 — `services.AddHttpClient()` registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
  • Outbound HTTP without resilience src/Web/Insightify.SPA/Insightify.SPA/Program.cs:13 — `new HttpClient { BaseAddress = new Uri(builder.HostEnvironment.BaseAddress) }` 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).
X3 · Exception handling · Rethrow loses stack trace (`throw ex;`) · ×2
  • Rethrow loses stack trace (`throw ex;`) src/Services/Insightify.Notifications/Insightify.Notifications/Services/NotificationService.cs:35 — `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.
  • Rethrow loses stack trace (`throw ex;`) src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Jobs/CryptoCurrencyJob.cs:46 — `throw ex;` resets the exception's stack trace to this line, hiding where it really came from. Use a bare `throw;` to preserve the original stack.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark src/Web/Insightify.MVC/Insightify.MVC/Views/Shared/_HomeLayout.cshtml:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 src/Web/Insightify.SPA/Insightify.SPA/Pages/News.razor:10 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.5 · ×1
  • Low contrast colour pair in CSS (1.5:1) src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/site.css:10 — `body` sets color: #D1D5DB on background-color: white — 1.5: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 (4.2 · ×1
  • Low contrast colour pair in CSS (4.2:1) src/Web/Insightify.MVC/Insightify.MVC/wwwroot/css/view-post-page.css:128 — `.post-container-main .post-content-container .post-content-data .post-hashtags .hashtag` sets color: white on background-color: #ba46d7 — 4.2: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 (4.0 · ×1
  • Low contrast colour pair in CSS (4.0:1) src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/wwwroot/css/account.css:51 — `.btn-primary` sets color: white on background-color: #b649f3 — 4.0: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 (@angular-eslint/eslint-plugin-template (a11y rules)) 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 42 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/News/NewsService.cs:26 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/News/NewsService.cs:26-47 | src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/Posts/PostService.cs:36-57 | src/Web/Insightify.MVC/Insightify.MVC/Services/News/NewsService.cs:24-45 | src/Web/Insightify.MVC/Insightify.MVC/Services/Posts/PostsService.cs:64-97 — 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 (112 lines × 4) · ×1
  • Duplicated block (112 lines × 4) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:250 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:250-361 | src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs:250-361 | src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Models/CryptoCurrencyModel.cs:249-360 | src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs:251-362 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs` and `src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 252 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:250` 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 (74 lines × 5) · ×1
  • Duplicated block (74 lines × 5) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:7 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:7-80 | src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/FinancialData/CryptoCurrencyOutputModel.cs:9-82 | src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs:7-80 | src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Models/CryptoCurrencyModel.cs:7-80 | src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs:8-81 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs` and `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/FinancialData/CryptoCurrencyOutputModel.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (34 lines × 4) · ×1
  • Duplicated block (34 lines × 4) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:184 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:184-217 | src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs:184-217 | src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Models/CryptoCurrencyModel.cs:183-216 | src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs:185-218 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs` and `src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 252 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 4) · ×1
  • Duplicated block (22 lines × 4) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:124 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:124-145 | src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs:124-145 | src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Models/CryptoCurrencyModel.cs:124-145 | src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs:125-146 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs` and `src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 252 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:124` 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 (20–21 lines × 3) · ×1
  • Duplicated block (20–21 lines × 3) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Infrastructure/Mapping/MappingProfile.cs:14 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Infrastructure/Mapping/MappingProfile.cs:14-34 | src/Services/Insightify.Posts/Insightify.Posts.Application/Common/Mapping/MappingProfile.cs:14-33 | src/Web/Insightify.MVC/Insightify.MVC/Infrastructure/Mapping/MappingProfile.cs:14-34 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Infrastructure/Mapping/MappingProfile.cs` and `src/Services/Insightify.Posts/Insightify.Posts.Application/Common/Mapping/MappingProfile.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Middleware/DatabaseMiddleware.cs:25 — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Middleware/DatabaseMiddleware.cs:25-43 | src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Middlewares/DatabaseMiddleware.cs:26-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:74 — src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:74-91 | src/Web/Insightify.MVC/Insightify.MVC/Services/UploadImage.cs:10-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Infrastructure/HttpClientAuthorizationDelegatingHandler.cs:18 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Infrastructure/HttpClientAuthorizationDelegatingHandler.cs:18-34 | src/Web/Insightify.MVC/Insightify.MVC/Infrastructure/HttpClientAuthorizationDelegatingHandler.cs:18-34 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Infrastructure/HttpClientAuthorizationDelegatingHandler.cs` and `src/Web/Insightify.MVC/Insightify.MVC/Infrastructure/HttpClientAuthorizationDelegatingHandler.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Posts/Configuration/LikeConfiguration.cs:15 — src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Posts/Configuration/LikeConfiguration.cs:15-29 | src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Posts/Configuration/SaveConfiguration.cs:15-30 — 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 `src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Posts/Configuration/LikeConfiguration.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<Like>` in one and `EntityTypeBuilder<Save>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/News/NewsService.cs:29 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/News/NewsService.cs:29-39 | src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/Posts/PostService.cs:39-49 | src/Web/Insightify.MVC/Insightify.MVC/Services/News/NewsService.cs:27-37 | src/Web/Insightify.MVC/Insightify.MVC/Services/Posts/PostsService.cs:67-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Middlewares/ExceptionHandlingMiddleware.cs:43 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Middlewares/ExceptionHandlingMiddleware.cs:43-57 | src/Services/Insightify.Posts/Insightify.Posts.Web/Middlewares/ValidationExceptionHandlerMiddleware.cs:45-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Middlewares/ExceptionHandlingMiddleware.cs:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/NewsArticleOutputModel.cs:9 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/NewsArticleOutputModel.cs:9-21 | src/Web/Insightify.MVC/Insightify.MVC/Clients/Models/NewsResponseModel.cs:5-17 | src/Web/Insightify.MVC/Insightify.MVC/Models/NewsViewModel.cs:8-20 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/NewsArticleOutputModel.cs` and `src/Web/Insightify.MVC/Insightify.MVC/Clients/Models/NewsResponseModel.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:172 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:172-181 | src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs:172-181 | src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Models/CryptoCurrencyModel.cs:171-180 | src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs:173-182 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs` and `src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 252 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:172` 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 (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/Posts/PostResponseModel.cs:5 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/Posts/PostResponseModel.cs:5-12 | src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/Posts/PostOutputModel.cs:8-15 | src/Web/Insightify.MVC/Insightify.MVC/Clients/Models/PostsResponseModel.cs:5-12 | src/Web/Insightify.MVC/Insightify.MVC/Models/Posts/PostViewModel.cs:8-15 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/Posts/PostOutputModel.cs` and `src/Web/Insightify.MVC/Insightify.MVC/Clients/Models/PostsResponseModel.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/News/NewsArticleResponseModel.cs:5 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/News/NewsArticleResponseModel.cs:5-12 | src/Web/Insightify.SPA/Insightify.SPA/Models/NewsArticle.cs:5-12 — before extracting anything, compare `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/News/NewsArticleResponseModel.cs` and `src/Web/Insightify.SPA/Insightify.SPA/Models/NewsArticle.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/Posts/CreatePostRequestModel.cs:7 — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/Posts/CreatePostRequestModel.cs:7-11 | src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/Posts/CreatePostInputModel.cs:4-8 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/Posts/CreatePostRequestModel.cs:7` 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 (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) src/Common/Insightify.Framework/Insightify.Framework.Pagination/Extensions/HeaderDictionaryExtensions.cs:26 — src/Common/Insightify.Framework/Insightify.Framework.Pagination/Extensions/HeaderDictionaryExtensions.cs:26-41 | src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Pagination/IHeaderDictionaryExtensions.cs:20-35 | src/Services/Insightify.Notifications/Insightify.Notifications/Pagination/IHeaderDictionaryExtensions.cs:20-35 — before extracting anything, compare `src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Pagination/IHeaderDictionaryExtensions.cs` and `src/Services/Insightify.Notifications/Insightify.Notifications/Pagination/IHeaderDictionaryExtensions.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Extensions/ServiceCollectionExtensions.cs:29 — src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Extensions/ServiceCollectionExtensions.cs:29-42 | src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Extensions/ServiceCollectionExtensions.cs:17-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) src/Common/Insightify.Framework/Insightify.Framework.Pagination/Headers/PaginationHeadersFilter.cs:18 — src/Common/Insightify.Framework/Insightify.Framework.Pagination/Headers/PaginationHeadersFilter.cs:18-28 | src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Pagination/PaginationHeadersFilter.cs:11-21 | src/Services/Insightify.Notifications/Insightify.Notifications/Pagination/PaginationHeadersFilter.cs:11-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Pagination/PagedList.cs:47 — src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Pagination/PagedList.cs:47-52 | src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Pagination/PagedList.cs:42-47 — before extracting anything, compare `src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Pagination/PagedList.cs` and `src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Pagination/PagedList.cs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET net7.0 REDACTED:4 — REDACTED declares .NET net7.0 as this project's target framework, and .NET 7, support ended 2024-05-14. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-05-14 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: Insightify.Framework src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:1 — Insightify.Framework: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Posts/Repositories/PostRepository.cs:108 — `GetPosts` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
P5 · DR & Backup · No DR/backup evidence · ×1
  • No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
R6 · Tooling · No lint script · ×1
  • No lint 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 (~15 LoC) · ×1
  • Dead file (~15 LoC) src/Web/Angular.Client/insightify-client/src/app/notifications/notification/notification.module.ts — no import path from any entry point (1 application, 0 tooling, 6 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
R8 · Dependency Hygiene · Unused dependency '@angular/forms' · ×1
  • Unused dependency '@angular/forms' — Declared in src/Web/Angular.Client/insightify-client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'bootstrap' · ×1
  • Unused dependency 'bootstrap' — Declared in src/Web/Angular.Client/insightify-client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'tslib' · ×1
  • Unused dependency 'tslib' — Declared in src/Web/Angular.Client/insightify-client/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Views/Account/Profile.cshtml:71 — `https://code.jquery.com/jquery-3.6.0.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. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 15 such include(s) across the repository's markup.
S1 · Web-Security Posture · Token validation disabled · ×1
  • Token validation disabled src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Extensions/ServiceCollectionExtensions.cs:68 — `ValidateAudience = false` means a token minted for a DIFFERENT relying party is accepted here. Any other service that trusts the same issuer can have its tokens replayed against this one, which is precisely what the `Audience` value exists to prevent.
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.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:35 — 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.
Minor — 158 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×39
  • Orphaned file src/Web/Insightify.MVC/Insightify.MVC/Models/FinancialData/CryptoCurrencyModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Clients/Models/FinancialData/CryptoCurrencyResponseModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Models/CryptoCurrencyModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Models/CryptoCurrencyModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Common/Insightify.Framework/Mongo/Insightify.Framework.MongoDb.Abstractions/Interfaces/IRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Controllers/AccountController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.Posts/Insightify.Posts.Infrastructure/Posts/Repositories/PostRepository.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Configuration/IdentityServerConfig.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Extensions/ProgramExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/Posts/PostService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Web/Insightify.MVC/Insightify.MVC/Services/Posts/PostsService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Web/Insightify.MVC/Insightify.MVC/Extensions/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Common/Insightify.Framework/Core/Insightify.Framework/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Web/Insightify.MVC/Insightify.MVC/Services/FinancialData/FinancialDataService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Common/Insightify.Framework/Core/Insightify.Framework/Swagger/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Models/FinancialData/CryptoCurrencyOutputModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.Friendship/Insightify.Friendship/Services/FriendshipService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Web/Insightify.MVC/Insightify.MVC/Common/LanguagePresets/Homepage.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.Notifications/Insightify.Notifications/Program.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Program.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Extensions/ServiceCollectionExtensions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Services/AccountSettings/AccountSettingsService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Services/Insightify.NewsAPI/Insightify.NewsAPI/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.
  • + 14 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×31
  • Outdated: Microsoft.AspNetCore.OpenApi REDACTED:36 — Microsoft.AspNetCore.OpenApi 7.0.9 → 10.0.13 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Microsoft.Extensions.DependencyInjection src/Common/Insightify.Framework/Messaging/Insightify.Framework.Messaging/Insightify.Framework.Messaging.csproj:18 — Microsoft.Extensions.DependencyInjection 7.0.0 → 10.0.13 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Microsoft.Extensions.DependencyInjection.Abstractions src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:23 — Microsoft.Extensions.DependencyInjection.Abstractions 7.0.0 → 10.0.13 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Microsoft.Extensions.Diagnostics.HealthChecks REDACTED:39 — Microsoft.Extensions.Diagnostics.HealthChecks 7.0.9 → 10.0.13 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Swashbuckle.AspNetCore src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:33 — Swashbuckle.AspNetCore 6.5.0 → 10.3.1 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Microsoft.AspNetCore.SignalR.Client src/Services/Insightify.Friendship/Insightify.Friendship/Insightify.Friendships.csproj:25 — Microsoft.AspNetCore.SignalR.Client 7.0.10 → 10.0.13 available (referenced by Insightify.Friendships).
  • Outdated: Microsoft.AspNetCore.Identity.EntityFrameworkCore REDACTED:21 — Microsoft.AspNetCore.Identity.EntityFrameworkCore 7.0.10 → 10.0.13 available (referenced by Insightify.IdentityAPI).
  • Outdated: Microsoft.EntityFrameworkCore src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:21 — Microsoft.EntityFrameworkCore 7.0.10 → 10.0.13 available (referenced by Insightify.IdentityAPI).
  • Outdated: Microsoft.EntityFrameworkCore.Design REDACTED:23 — Microsoft.EntityFrameworkCore.Design 7.0.10 → 10.0.13 available (referenced by Insightify.IdentityAPI).
  • Outdated: Microsoft.EntityFrameworkCore.SqlServer src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:22 — Microsoft.EntityFrameworkCore.SqlServer 7.0.10 → 10.0.13 available (referenced by Insightify.IdentityAPI).
  • Outdated: Microsoft.EntityFrameworkCore.Tools REDACTED:28 — Microsoft.EntityFrameworkCore.Tools 7.0.10 → 10.0.13 available (referenced by Insightify.IdentityAPI).
  • Outdated: Serilog.AspNetCore src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:25 — Serilog.AspNetCore 7.0.0 → 10.0.0 available (referenced by Insightify.IdentityAPI).
  • Outdated: Serilog.Sinks.Seq src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:28 — Serilog.Sinks.Seq 5.2.2 → 9.1.0 available (referenced by Insightify.IdentityAPI).
  • Outdated: Microsoft.AspNetCore.Authentication.JwtBearer src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:32 — Microsoft.AspNetCore.Authentication.JwtBearer 7.0.10 → 10.0.13 available (referenced by Insightify.NewsAPI).
  • Outdated: Serilog.Settings.Configuration src/Common/Insightify.Framework/Logging/Insightify.Framework.Logging/Insightify.Framework.Logging.csproj:19 — Serilog.Settings.Configuration 7.0.0 → 10.0.1 available (referenced by Insightify.NewsAPI).
  • Outdated: AutoMapper src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:18 — REDACTED → 16.2.0 available (referenced by Insightify.NewsBackgroundTasks).
  • Outdated: Microsoft.Extensions.Hosting src/Common/Insightify.Framework/Logging/Insightify.Framework.Logging/Insightify.Framework.Logging.csproj:15 — Microsoft.Extensions.Hosting 7.0.1 → 10.0.13 available (referenced by Insightify.NewsBackgroundTasks).
  • Outdated: Microsoft.Extensions.Configuration src/Services/Insightify.Posts/Insightify.Posts.Application/Insightify.Posts.Application.csproj:15 — Microsoft.Extensions.Configuration 7.0.0 → 10.0.13 available (referenced by Insightify.Posts.Application).
  • Outdated: Microsoft.Extensions.Options src/Common/Insightify.Framework/Fetching/Insightify.Framework.Fetching/Insightify.Framework.Fetching.csproj:16 — Microsoft.Extensions.Options 7.0.1 → 10.0.13 available (referenced by Insightify.Posts.Application).
  • Outdated: Scrutor REDACTED:14 — Scrutor 4.2.2 → 7.0.0 available (referenced by Insightify.Posts.Domain).
  • Outdated: Refit REDACTED:18 — REDACTED → 16.4.0 available (referenced by Insightify.Web.Gateway).
  • Outdated: Refit.HttpClientFactory REDACTED:19 — Refit.HttpClientFactory 7.0.0 → 16.4.0 available (referenced by Insightify.Web.Gateway).
  • Outdated: Refit.Newtonsoft.Json REDACTED:20 — Refit.Newtonsoft.Json 7.0.0 → 16.4.0 available (referenced by Insightify.Web.Gateway).
  • Outdated: Microsoft.AspNetCore.Mvc.NewtonsoftJson src/Common/Insightify.Framework/Core/Insightify.Framework/Insightify.Framework.csproj:20 — Microsoft.AspNetCore.Mvc.NewtonsoftJson 7.0.10 → 10.0.13 available (referenced by Insightify.Framework).
  • Outdated: Microsoft.Extensions.Http src/Common/Insightify.Framework/Fetching/Insightify.Framework.Fetching/Insightify.Framework.Fetching.csproj:15 — Microsoft.Extensions.Http 7.0.0 → 10.0.13 available (referenced by Insightify.Framework.Fetching).
  • + 6 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×17
  • Interpolated log message defeats structured logging src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Services/NewsReadService.cs:42 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Services/NewsService.cs:37 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Services/NewsService.cs:51 — 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 src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Services/NewsService.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 src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/Posts/PostService.cs:78 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Services/Posts/PostService.cs:106 — 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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:48 — 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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:64 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:113 — 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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:122 — 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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:152 — 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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:162 — 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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:178 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:215 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:261 — 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 src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:291 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
S1 · Web-Security Posture · No security response headers detected · ×11
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Program.cs:21 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Program.cs:16 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Services/Insighify.FinancialDataApi/Insightify.FinancialBackgroundTasks/Program.cs:12 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Services/Insightify.Friendship/Insightify.Friendship/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.
  • No security response headers detected src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Program.cs:13 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Services/Insightify.NewsAPI/Insightify.NewsAPI/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.
  • No security response headers detected src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Program.cs:23 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Services/Insightify.Notifications/Insightify.Notifications/Program.cs:23 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Services/Insightify.Posts/Insightify.Posts.Startup/Program.cs:13 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
  • No security response headers detected src/Web/Insightify.MVC/Insightify.MVC/Program.cs:10 — 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.
D12 · Dependency Hygiene · Outdated (npm) · ×9
  • Outdated (npm): @angular/animations src/Web/Angular.Client/insightify-client/package.json:13 — @angular/animations 16.0.2 → 22.2.3 available.
  • Outdated (npm): @angular/common src/Web/Angular.Client/insightify-client/package.json:14 — @angular/common 16.0.2 → 22.2.3 available.
  • Outdated (npm): @angular/compiler src/Web/Angular.Client/insightify-client/package.json:15 — @angular/compiler 16.0.2 → 22.2.3 available.
  • Outdated (npm): @angular/core src/Web/Angular.Client/insightify-client/package.json:16 — @angular/core 16.0.2 → 22.2.3 available.
  • Outdated (npm): @angular/forms src/Web/Angular.Client/insightify-client/package.json:17 — @angular/forms 16.0.2 → 22.2.3 available.
  • Outdated (npm): @angular/platform-browser src/Web/Angular.Client/insightify-client/package.json:18 — @angular/platform-browser 16.0.2 → 22.2.3 available.
  • Outdated (npm): @angular/platform-browser-dynamic src/Web/Angular.Client/insightify-client/package.json:19 — @angular/platform-browser-dynamic 16.0.2 → 22.2.3 available.
  • Outdated (npm): @angular/router src/Web/Angular.Client/insightify-client/package.json:20 — @angular/router 16.0.2 → 22.2.3 available.
  • Outdated (npm): serialize-javascript — serialize-javascript 4.0.0 → 7.1.2 available.
D30 · Dependency Vulnerabilities · Low CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Commented-out code · ×4
  • Commented-out code src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Middlewares/ExceptionHandlingMiddleware.cs:42 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Program.cs:52 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Services/Insightify.NewsAPI/Insightify.NewsBackgroundTasks/Program.cs:25 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code src/Web/Insightify.MVC/Insightify.MVC/Extensions/ServiceCollectionExtensions.cs:31 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Services/NewsReadService.cs:20 — `articles == null || articles.TotalCount == 0` appears character-identically in 2 files — src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Services/NewsReadService.cs, src/Services/Insightify.Notifications/Insightify.Notifications/Services/NotificationService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Pagination/PaginationHeadersFilter.cs:11 — `context.Result is ObjectResult objectResult && objectResult.Value is IPage page` appears character-identically in 3 files — src/Common/Insightify.Framework/Insightify.Framework.Pagination/Headers/PaginationHeadersFilter.cs, src/Services/Insightify.NewsAPI/Insightify.NewsAPI/Pagination/PaginationHeadersFilter.cs, src/Services/Insightify.Notifications/Insightify.Notifications/Pagination/PaginationHeadersFilter.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Services/Insightify.Posts/Insightify.Posts.Application/Common/Mapping/MappingProfile.cs:19 — `i.IsGenericType && i.GetGenericTypeDefinition() == typeof(IMapFrom<>)` appears character-identically in 3 files — src/Gateways/Insightify.Web.Gateway/Insightify.Web.Gateway/Infrastructure/Mapping/MappingProfile.cs, src/Services/Insightify.Posts/Insightify.Posts.Application/Common/Mapping/MappingProfile.cs, src/Web/Insightify.MVC/Insightify.MVC/Infrastructure/Mapping/MappingProfile.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×2
  • Diagnostic log message is built whether or not it is wanted src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:64 — `LogDebug` at line 64 is called with an argument built by `string.Join(", ", entities.Select(e => e.Id))` (line 64), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
  • Diagnostic log message is built whether or not it is wanted src/Common/Insightify.Framework/Mongo/Insigghtify.Framework.Mongo/Repository.cs:178 — `LogDebug` at line 178 is called with an argument built by `string.Join(", ", entities.Select(e => e.Id))` (line 178), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IRepository<T> (17 members) src/Common/Insightify.Framework/Mongo/Insightify.Framework.MongoDb.Abstractions/Interfaces/IRepository.cs:8 — `IRepository<T>` declares 17 members under just 15 distinct name(s): `InsertAsync`, `InsertAsync`, `UpdateAsync`, `DeleteByIdAsync`, `DeleteAsync`, `DeleteAsync`, `DeleteOneAsync`, `DeleteManyAsync`, `RestoreAsync`, `RestoreByIdAsync`, `CountAsync`, `ExistsAsync`, `GetByIdAsync`, `GetAllAsync`, `GetPagedListAsync`, `GetFirstOrDefaultAsync`, `GetSingleOrDefaultAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
C2 · Access Controls · Anonymous-heavy surface · ×1
  • Anonymous-heavy surface — [AllowAnonymous] (12) outweighs [Authorize] (6) — review whether the open surface is intended.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
D10 · Test Quality · Mock-dominated test · ×1
  • Mock-dominated test: Delete_Should_Delete_Article_When_Article_Found src/Services/Insightify.NewsAPI/Insightify.NewsAPI.Tests/NewsServiceTests.cs:80 — This test sets up 4 test doubles (for example `new Mock<ILogger<NewsService>>()`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: @npmcli/move-file REDACTED:2887 — @npmcli/move-file 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
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 · Spelling error · ×1
  • Spelling error: 'Opperations' vs 'Operations'. The type name contains a typo in the word 'Operations'. — Rename to 'CryptoCoinsOperations' (symbols: Insightify.FinancialDataApi.Configuration.UrlsConfig.CryptoCoinsOpperations, Insightify.FinancialBackgroundTasks.Models.CryptoCurrencyModel)
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 39 of 39 significant files have no living knowledge — the codebase as a whole is dormant, not 39 separate risks. Counted over 39 of the 301 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift README.md:6 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 48/48 types (100%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 14/20 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 20, 9 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
PF2 · Allocation hygiene · No allocation-aware APIs detected · ×1
  • No allocation-aware APIs detected — No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.
S1 · Web-Security Posture · OIDC metadata fetched over HTTP · ×1
  • OIDC metadata fetched over HTTP src/Services/Insighify.FinancialDataApi/Insighify.FinancialDataApi/Extensions/ServiceCollectionExtensions.cs:49 — `RequireHttpsMetadata = false` allows the OIDC discovery doc to be fetched over plain HTTP. Safe for loopback-only fetches (Aspire / on-host); risky for any other path.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 34/147 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 — 22/23 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.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~2.0 `!` suppressions per 1k syntax nodes — 130 suppression(s) across the 66283 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 53 finding(s)
D12 · Dependency Hygiene · Outdated · ×41
  • Outdated: AspNetCore.HealthChecks.MongoDb — AspNetCore.HealthChecks.MongoDb 7.0.0 → 9.0.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: FluentValidation — FluentValidation 11.6.0 → 12.2.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: FluentValidation.DependencyInjectionExtensions — FluentValidation.DependencyInjectionExtensions 11.6.0 → 12.2.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Microsoft.VisualStudio.Azure.Containers.Tools.Targets — Microsoft.VisualStudio.Azure.Containers.Tools.Targets 1.18.1 → 1.23.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: MongoDB.Driver — MongoDB.Driver 2.20.0 → 3.12.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Quartz — Quartz 3.7.0 → 4.6.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Quartz.Extensions.DependencyInjection — Quartz.Extensions.DependencyInjection 3.7.0 → 4.6.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Quartz.Extensions.Hosting — Quartz.Extensions.Hosting 3.7.0 → 4.6.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Quartz.Jobs — Quartz.Jobs 3.7.0 → 4.6.0 available (referenced by Insighify.FinancialDataApi).
  • Outdated: StackExchange.Redis — StackExchange.Redis 2.7.4 → 3.4.5 available (referenced by Insighify.FinancialDataApi).
  • Outdated: Insightify.Framework.Messaging — Insightify.Framework.Messaging 1.0.0 → 1.0.2 available (referenced by Insightify.Friendships).
  • Outdated: Insightify.Framework.Messaging.Abstractions — Insightify.Framework.Messaging.Abstractions 1.0.0 → 1.0.2 available (referenced by Insightify.Friendships).
  • Outdated: RabbitMQ.Client — RabbitMQ.Client 6.5.0 → 7.2.2 available (referenced by Insightify.Friendships).
  • Outdated: AspNetCore.HealthChecks.SqlServer — AspNetCore.HealthChecks.SqlServer 7.0.0 → 9.0.0 available (referenced by Insightify.IdentityAPI).
  • Outdated: AspNetCore.HealthChecks.UI — AspNetCore.HealthChecks.UI 7.0.2 → 9.0.0 available (referenced by Insightify.IdentityAPI).
  • Outdated: AspNetCore.HealthChecks.UI.Client — AspNetCore.HealthChecks.UI.Client 7.1.0 → 9.0.0 available (referenced by Insightify.IdentityAPI).
  • Outdated: AspNetCore.HealthChecks.UI.InMemory.Storage — AspNetCore.HealthChecks.UI.InMemory.Storage 7.0.0 → 9.0.0 available (referenced by Insightify.IdentityAPI).
  • Outdated: Duende.IdentityServer — REDACTED → 8.0.10 available (referenced by Insightify.IdentityAPI).
  • Outdated: Duende.IdentityServer.AspNetIdentity — Duende.IdentityServer.AspNetIdentity 6.3.3 → 8.0.10 available (referenced by Insightify.IdentityAPI).
  • Outdated: MailKit — REDACTED → 4.18.1 available (referenced by Insightify.IdentityAPI).
  • Outdated: Newtonsoft.Json — Newtonsoft.Json 13.0.3 → 13.0.4 available (referenced by Insightify.IdentityAPI).
  • Outdated: Polly — Polly 7.2.4 → 8.8.0 available (referenced by Insightify.IdentityAPI).
  • Outdated: Serilog.Enrichers.Environment — Serilog.Enrichers.Environment 2.2.0 → 3.0.1 available (referenced by Insightify.IdentityAPI).
  • Outdated: Serilog.Sinks.Http — Serilog.Sinks.Http 8.0.0 → 9.2.1 available (referenced by Insightify.IdentityAPI).
  • Outdated: Serilog — Serilog 3.0.1 → 4.4.0 available (referenced by Insightify.NewsAPI).
  • + 16 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated (npm) · ×8
  • Outdated (npm): @popperjs/core — @popperjs/core 2.11.7 → 2.11.8 available.
  • Outdated (npm): acorn — acorn 7.4.1 → 8.19.0 available.
  • Outdated (npm): bootstrap — bootstrap 5.2.3 → 5.3.8 available.
  • Outdated (npm): core-js — core-js 3.30.2 → 3.51.0 available.
  • Outdated (npm): crypto-js — crypto-js 4.1.1 → 4.2.0 available.
  • Outdated (npm): rxjs — rxjs 7.8.1 → 7.8.2 available.
  • Outdated (npm): tslib — tslib 2.5.2 → 2.8.1 available.
  • Outdated (npm): zone.js — zone.js 0.13.0 → 0.16.3 available.
D10 · Test Quality · Mock framework · ×4
  • Mock framework: Moq — Insightify.Posts.Domain references Moq.
  • Mock framework: Moq — Insightify.Framework.Mongo.Tests references Moq.
  • Mock framework: Moq — Insightify.Framework.Tests references Moq.
  • Mock framework: Moq — Insightify.NewsAPI.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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-97f409d9c35d4779a7361ccce2fc6feb/history.json --exit-code 0 --source .3artifacts/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-97f409d9c35d4779a7361ccce2fc6feb/tree.json --exit-code 0 --source .1artifacts/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 .139artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list Insightify.sln package --vulnerable --include-transitive --format json110artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .48artifacts/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.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a1610d-4d07-789e-859f-d891ad6bc475 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

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

Email — 2 field(s)
  • ApplicationUserEditModel.Email src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/Models/ApplicationUserEditModel.cs:7
  • RegisterInputViewModel.Email src/Services/Insightify.IdentityAPI/Insightify.IdentityAPI/ViewModels/RegisterInputViewModel.cs:11

Issues: 234 · Warnings: 295 · Recommendations: 158 · Info: 53 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 00:40 UTC.

Downloadable artifacts

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

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