Executive summary
NitroDevs/FShopOnWeb falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 51 out of 100 and is rated Adequate, and all 17 of its critical findings are security problems in the packages it uses and in the build pipeline.
Production Readiness, at 38, is the weakest lens and counts most in the score. The best first step is adding tests for untested code, worth about 11 points. Logging through a logging library would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 61.
Thirteen known security holes in the packages the code depends on can be used by attackers. Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks.
The product code is 795 lines, too few for a meaningful rebuild estimate.
If Production Readiness rose from 38 to 70, the lowest score rated Strong, the score would rise from 51 to about 61.
New since the last survey: 9 findings
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Layout/_basket.scss
- Visual & motion safety · Low contrast colour pair in CSS (4.0:1) src/Microsoft.eShopWeb.Web/Layout/_basket.scss
- Visual & motion safety · Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Home/_catalogFilters.scss
- Visual & motion safety · Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Home/_index.scss
- Visual & motion safety · Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Home/_productsGrid.scss
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Microsoft.eShopWeb.Web/Layout/_identity.scss
- Visual & motion safety · Animation without a prefers-reduced-motion guard src/Microsoft.eShopWeb.Web/Layout/_identity.scss
Fixed since the last survey: 8 findings
- Static Analysis (SAST) · Medium: watchdog-eol-dotnet-runtime-in-workflow REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Supply-chain Provenance & Signing REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net9.0
- Page structure · Document without a <title> src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs
- Page structure · Page without a main landmark src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs
- Page structure · Document without a <title> src/Microsoft.eShopWeb.Web/Layout/Public.Layout.fs
- Page structure · Page without a main landmark src/Microsoft.eShopWeb.Web/Layout/Public.Layout.fs
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 EFCoreFSharp | 2 Microsoft.eShopWeb.Web.Async | 3 Microsoft.eShopWeb.Web.Basket.BasketPage | 4 Microsoft.eShopWeb.Web.Domain | 5 Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent | 6 Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent.Template | 7 Microsoft.eShopWeb.Web.Home.CatalogPagerComponent | 8 Microsoft.eShopWeb.Web.Program | 9 Microsoft.eShopWeb.Web.Request | 10 Microsoft.eShopWeb.Web.Account.Login.LoginPage | 11 Microsoft.eShopWeb.Web.AccountLayout | 12 Microsoft.eShopWeb.Web.BasketComponent | 13 Microsoft.eShopWeb.Web.BasketComponent.Template | 14 Microsoft.eShopWeb.Web.Home.CatalogGridComponent | 15 Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template | 16 Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template | 17 Microsoft.eShopWeb.Web.Persistence | 18 Microsoft.eShopWeb.Web.Persistence.Seeding | 19 Microsoft.eShopWeb.Web.PublicLayout | 20 Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template | 21 Microsoft.eShopWeb.Web.AccountLayout.Template | 22 Microsoft.eShopWeb.Web.Basket.BasketDomain | 23 Microsoft.eShopWeb.Web.Basket.BasketPage.Template | 24 Microsoft.eShopWeb.Web.Home.HomePage | 25 Microsoft.eShopWeb.Web.PublicLayout.Template | 26 Microsoft.eShopWeb.Web.Home.HomePage.Template |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 EFCoreFSharp | ||||||||||||||||||||||||||
| 2 Microsoft.eShopWeb.Web.Async | ||||||||||||||||||||||||||
| 3 Microsoft.eShopWeb.Web.Basket.BasketPage | ||||||||||||||||||||||||||
| 4 Microsoft.eShopWeb.Web.Domain | ||||||||||||||||||||||||||
| 5 Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent | ||||||||||||||||||||||||||
| 6 Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent.Template | ||||||||||||||||||||||||||
| 7 Microsoft.eShopWeb.Web.Home.CatalogPagerComponent | ||||||||||||||||||||||||||
| 8 Microsoft.eShopWeb.Web.Program | ||||||||||||||||||||||||||
| 9 Microsoft.eShopWeb.Web.Request | ||||||||||||||||||||||||||
| 10 Microsoft.eShopWeb.Web.Account.Login.LoginPage | 1 | |||||||||||||||||||||||||
| 11 Microsoft.eShopWeb.Web.AccountLayout | 1 | |||||||||||||||||||||||||
| 12 Microsoft.eShopWeb.Web.BasketComponent | 1 | |||||||||||||||||||||||||
| 13 Microsoft.eShopWeb.Web.BasketComponent.Template | 1 | |||||||||||||||||||||||||
| 14 Microsoft.eShopWeb.Web.Home.CatalogGridComponent | 1 | |||||||||||||||||||||||||
| 15 Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template | 1 | |||||||||||||||||||||||||
| 16 Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template | 1 | |||||||||||||||||||||||||
| 17 Microsoft.eShopWeb.Web.Persistence | 3 | |||||||||||||||||||||||||
| 18 Microsoft.eShopWeb.Web.Persistence.Seeding | 3 | |||||||||||||||||||||||||
| 19 Microsoft.eShopWeb.Web.PublicLayout | 1 | |||||||||||||||||||||||||
| 20 Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template | 1 | 1 | ||||||||||||||||||||||||
| 21 Microsoft.eShopWeb.Web.AccountLayout.Template | 1 | 1 | ||||||||||||||||||||||||
| 22 Microsoft.eShopWeb.Web.Basket.BasketDomain | 3 | 1 | ||||||||||||||||||||||||
| 23 Microsoft.eShopWeb.Web.Basket.BasketPage.Template | 1 | 1 | ||||||||||||||||||||||||
| 24 Microsoft.eShopWeb.Web.Home.HomePage | 1 | 1 | 1 | 1 | ||||||||||||||||||||||
| 25 Microsoft.eShopWeb.Web.PublicLayout.Template | 1 | 1 | ||||||||||||||||||||||||
| 26 Microsoft.eShopWeb.Web.Home.HomePage.Template | 1 | 1 | 1 |
10→4 Microsoft.eShopWeb.Web.Account.Login.LoginPage uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Account.Login.LoginPage uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Account.Login.LoginPage.Props→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.Account.Login.LoginPage uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Account.Login.LoginPage, while a change to Microsoft.eShopWeb.Web.Account.Login.LoginPage can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Account.Login.LoginPage uses a module listed above it, which is the healthy direction.
11→4 Microsoft.eShopWeb.Web.AccountLayout uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.AccountLayout uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.AccountLayout.AccountLayout→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.AccountLayout uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.AccountLayout, while a change to Microsoft.eShopWeb.Web.AccountLayout can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.AccountLayout uses a module listed above it, which is the healthy direction.
12→4 Microsoft.eShopWeb.Web.BasketComponent uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.BasketComponent uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.BasketComponent.BasketComponent→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.BasketComponent uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.BasketComponent, while a change to Microsoft.eShopWeb.Web.BasketComponent can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.BasketComponent uses a module listed above it, which is the healthy direction.
13→4 Microsoft.eShopWeb.Web.BasketComponent.Template uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.BasketComponent.Template uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.BasketComponent.Template.Template→Microsoft.eShopWeb.Web.Domain.BasketItem
- Direction
- Microsoft.eShopWeb.Web.BasketComponent.Template uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.BasketComponent.Template, while a change to Microsoft.eShopWeb.Web.BasketComponent.Template can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.BasketComponent.Template uses a module listed above it, which is the healthy direction.
14→4 Microsoft.eShopWeb.Web.Home.CatalogGridComponent uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.CatalogGridComponent uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Props→Microsoft.eShopWeb.Web.Domain.CatalogItem
- Direction
- Microsoft.eShopWeb.Web.Home.CatalogGridComponent uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Home.CatalogGridComponent, while a change to Microsoft.eShopWeb.Web.Home.CatalogGridComponent can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.CatalogGridComponent uses a module listed above it, which is the healthy direction.
15→4 Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template.Template→Microsoft.eShopWeb.Web.Domain.CatalogItem
- Direction
- Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template, while a change to Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Template uses a module listed above it, which is the healthy direction.
16→7 Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template uses Microsoft.eShopWeb.Web.Home.CatalogPagerComponent✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template uses a type in Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.
- The types involved
Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template.Template→Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Props
- Direction
- Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template uses Microsoft.eShopWeb.Web.Home.CatalogPagerComponent, so a change to Microsoft.eShopWeb.Web.Home.CatalogPagerComponent can break Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template, while a change to Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template can't break Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Template uses a module listed above it, which is the healthy direction.
17→4 Microsoft.eShopWeb.Web.Persistence uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 3 pairs of types, where a type in Microsoft.eShopWeb.Web.Persistence uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Persistence.ShopContext→Microsoft.eShopWeb.Web.Domain.BasketMicrosoft.eShopWeb.Web.Persistence.ShopContext→Microsoft.eShopWeb.Web.Domain.BasketItemMicrosoft.eShopWeb.Web.Persistence.ShopContext→Microsoft.eShopWeb.Web.Domain.CatalogItem
- Direction
- Microsoft.eShopWeb.Web.Persistence uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Persistence, while a change to Microsoft.eShopWeb.Web.Persistence can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Persistence uses a module listed above it, which is the healthy direction.
18→4 Microsoft.eShopWeb.Web.Persistence.Seeding uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 3 pairs of types, where a type in Microsoft.eShopWeb.Web.Persistence.Seeding uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Persistence.Seeding.CatalogBrands→Microsoft.eShopWeb.Web.Domain.CatalogBrandMicrosoft.eShopWeb.Web.Persistence.Seeding.CatalogTypes→Microsoft.eShopWeb.Web.Domain.CatalogTypeMicrosoft.eShopWeb.Web.Persistence.Seeding.Seeding→Microsoft.eShopWeb.Web.Domain.CatalogItem
- Direction
- Microsoft.eShopWeb.Web.Persistence.Seeding uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Persistence.Seeding, while a change to Microsoft.eShopWeb.Web.Persistence.Seeding can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Persistence.Seeding uses a module listed above it, which is the healthy direction.
19→4 Microsoft.eShopWeb.Web.PublicLayout uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.PublicLayout uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.PublicLayout.PublicLayout→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.PublicLayout uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.PublicLayout, while a change to Microsoft.eShopWeb.Web.PublicLayout can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.PublicLayout uses a module listed above it, which is the healthy direction.
20→10 Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses Microsoft.eShopWeb.Web.Account.Login.LoginPage✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses a type in Microsoft.eShopWeb.Web.Account.Login.LoginPage.
- The types involved
Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template.Template→Microsoft.eShopWeb.Web.Account.Login.LoginPage.Props
- Direction
- Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses Microsoft.eShopWeb.Web.Account.Login.LoginPage, so a change to Microsoft.eShopWeb.Web.Account.Login.LoginPage can break Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template, while a change to Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template can't break Microsoft.eShopWeb.Web.Account.Login.LoginPage.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses a module listed above it, which is the healthy direction.
20→11 Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses Microsoft.eShopWeb.Web.AccountLayout✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses a type in Microsoft.eShopWeb.Web.AccountLayout.
- The types involved
Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template.Template→Microsoft.eShopWeb.Web.AccountLayout.HeadMetadata
- Direction
- Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses Microsoft.eShopWeb.Web.AccountLayout, so a change to Microsoft.eShopWeb.Web.AccountLayout can break Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template, while a change to Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template can't break Microsoft.eShopWeb.Web.AccountLayout.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Account.Login.LoginPage.Template uses a module listed above it, which is the healthy direction.
21→4 Microsoft.eShopWeb.Web.AccountLayout.Template uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.AccountLayout.Template uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.AccountLayout.Template.Template→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.AccountLayout.Template uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.AccountLayout.Template, while a change to Microsoft.eShopWeb.Web.AccountLayout.Template can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.AccountLayout.Template uses a module listed above it, which is the healthy direction.
21→11 Microsoft.eShopWeb.Web.AccountLayout.Template uses Microsoft.eShopWeb.Web.AccountLayout✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.AccountLayout.Template uses a type in Microsoft.eShopWeb.Web.AccountLayout.
- The types involved
Microsoft.eShopWeb.Web.AccountLayout.Template.Template→Microsoft.eShopWeb.Web.AccountLayout.HeadMetadata
- Direction
- Microsoft.eShopWeb.Web.AccountLayout.Template uses Microsoft.eShopWeb.Web.AccountLayout, so a change to Microsoft.eShopWeb.Web.AccountLayout can break Microsoft.eShopWeb.Web.AccountLayout.Template, while a change to Microsoft.eShopWeb.Web.AccountLayout.Template can't break Microsoft.eShopWeb.Web.AccountLayout.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.AccountLayout.Template uses a module listed above it, which is the healthy direction.
22→4 Microsoft.eShopWeb.Web.Basket.BasketDomain uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 3 pairs of types, where a type in Microsoft.eShopWeb.Web.Basket.BasketDomain uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Basket.BasketDomain.BasketDomain→Microsoft.eShopWeb.Web.Domain.BasketMicrosoft.eShopWeb.Web.Basket.BasketDomain.BasketDomain→Microsoft.eShopWeb.Web.Domain.BasketItemMicrosoft.eShopWeb.Web.Basket.BasketDomain.BasketDomain→Microsoft.eShopWeb.Web.Domain.CatalogItem
- Direction
- Microsoft.eShopWeb.Web.Basket.BasketDomain uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Basket.BasketDomain, while a change to Microsoft.eShopWeb.Web.Basket.BasketDomain can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Basket.BasketDomain uses a module listed above it, which is the healthy direction.
22→17 Microsoft.eShopWeb.Web.Basket.BasketDomain uses Microsoft.eShopWeb.Web.Persistence✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Basket.BasketDomain uses a type in Microsoft.eShopWeb.Web.Persistence.
- The types involved
Microsoft.eShopWeb.Web.Basket.BasketDomain.BasketDomain→Microsoft.eShopWeb.Web.Persistence.ShopContext
- Direction
- Microsoft.eShopWeb.Web.Basket.BasketDomain uses Microsoft.eShopWeb.Web.Persistence, so a change to Microsoft.eShopWeb.Web.Persistence can break Microsoft.eShopWeb.Web.Basket.BasketDomain, while a change to Microsoft.eShopWeb.Web.Basket.BasketDomain can't break Microsoft.eShopWeb.Web.Persistence.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Basket.BasketDomain uses a module listed above it, which is the healthy direction.
23→4 Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Basket.BasketPage.Template.Template→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Basket.BasketPage.Template, while a change to Microsoft.eShopWeb.Web.Basket.BasketPage.Template can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses a module listed above it, which is the healthy direction.
23→19 Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses Microsoft.eShopWeb.Web.PublicLayout✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses a type in Microsoft.eShopWeb.Web.PublicLayout.
- The types involved
Microsoft.eShopWeb.Web.Basket.BasketPage.Template.Template→Microsoft.eShopWeb.Web.PublicLayout.HeadMetadata
- Direction
- Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses Microsoft.eShopWeb.Web.PublicLayout, so a change to Microsoft.eShopWeb.Web.PublicLayout can break Microsoft.eShopWeb.Web.Basket.BasketPage.Template, while a change to Microsoft.eShopWeb.Web.Basket.BasketPage.Template can't break Microsoft.eShopWeb.Web.PublicLayout.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Basket.BasketPage.Template uses a module listed above it, which is the healthy direction.
24→4 Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.HomePage uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.Home.HomePage.Props→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.Home.HomePage, while a change to Microsoft.eShopWeb.Web.Home.HomePage can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.HomePage uses a module listed above it, which is the healthy direction.
24→5 Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.HomePage uses a type in Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent.
- The types involved
Microsoft.eShopWeb.Web.Home.HomePage.Props→Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent.Props
- Direction
- Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent, so a change to Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent can break Microsoft.eShopWeb.Web.Home.HomePage, while a change to Microsoft.eShopWeb.Web.Home.HomePage can't break Microsoft.eShopWeb.Web.Home.CatalogFiltersComponent.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.HomePage uses a module listed above it, which is the healthy direction.
24→7 Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Home.CatalogPagerComponent✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.HomePage uses a type in Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.
- The types involved
Microsoft.eShopWeb.Web.Home.HomePage.Props→Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.Props
- Direction
- Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Home.CatalogPagerComponent, so a change to Microsoft.eShopWeb.Web.Home.CatalogPagerComponent can break Microsoft.eShopWeb.Web.Home.HomePage, while a change to Microsoft.eShopWeb.Web.Home.HomePage can't break Microsoft.eShopWeb.Web.Home.CatalogPagerComponent.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.HomePage uses a module listed above it, which is the healthy direction.
24→14 Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Home.CatalogGridComponent✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.HomePage uses a type in Microsoft.eShopWeb.Web.Home.CatalogGridComponent.
- The types involved
Microsoft.eShopWeb.Web.Home.HomePage.Props→Microsoft.eShopWeb.Web.Home.CatalogGridComponent.Props
- Direction
- Microsoft.eShopWeb.Web.Home.HomePage uses Microsoft.eShopWeb.Web.Home.CatalogGridComponent, so a change to Microsoft.eShopWeb.Web.Home.CatalogGridComponent can break Microsoft.eShopWeb.Web.Home.HomePage, while a change to Microsoft.eShopWeb.Web.Home.HomePage can't break Microsoft.eShopWeb.Web.Home.CatalogGridComponent.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.HomePage uses a module listed above it, which is the healthy direction.
25→4 Microsoft.eShopWeb.Web.PublicLayout.Template uses Microsoft.eShopWeb.Web.Domain✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.PublicLayout.Template uses a type in Microsoft.eShopWeb.Web.Domain.
- The types involved
Microsoft.eShopWeb.Web.PublicLayout.Template.Template→Microsoft.eShopWeb.Web.Domain.Basket
- Direction
- Microsoft.eShopWeb.Web.PublicLayout.Template uses Microsoft.eShopWeb.Web.Domain, so a change to Microsoft.eShopWeb.Web.Domain can break Microsoft.eShopWeb.Web.PublicLayout.Template, while a change to Microsoft.eShopWeb.Web.PublicLayout.Template can't break Microsoft.eShopWeb.Web.Domain.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.PublicLayout.Template uses a module listed above it, which is the healthy direction.
25→19 Microsoft.eShopWeb.Web.PublicLayout.Template uses Microsoft.eShopWeb.Web.PublicLayout✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.PublicLayout.Template uses a type in Microsoft.eShopWeb.Web.PublicLayout.
- The types involved
Microsoft.eShopWeb.Web.PublicLayout.Template.Template→Microsoft.eShopWeb.Web.PublicLayout.HeadMetadata
- Direction
- Microsoft.eShopWeb.Web.PublicLayout.Template uses Microsoft.eShopWeb.Web.PublicLayout, so a change to Microsoft.eShopWeb.Web.PublicLayout can break Microsoft.eShopWeb.Web.PublicLayout.Template, while a change to Microsoft.eShopWeb.Web.PublicLayout.Template can't break Microsoft.eShopWeb.Web.PublicLayout.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.PublicLayout.Template uses a module listed above it, which is the healthy direction.
26→17 Microsoft.eShopWeb.Web.Home.HomePage.Template uses Microsoft.eShopWeb.Web.Persistence✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.HomePage.Template uses a type in Microsoft.eShopWeb.Web.Persistence.
- The types involved
Microsoft.eShopWeb.Web.Home.HomePage.Template.Template→Microsoft.eShopWeb.Web.Persistence.ShopContext
- Direction
- Microsoft.eShopWeb.Web.Home.HomePage.Template uses Microsoft.eShopWeb.Web.Persistence, so a change to Microsoft.eShopWeb.Web.Persistence can break Microsoft.eShopWeb.Web.Home.HomePage.Template, while a change to Microsoft.eShopWeb.Web.Home.HomePage.Template can't break Microsoft.eShopWeb.Web.Persistence.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.HomePage.Template uses a module listed above it, which is the healthy direction.
26→19 Microsoft.eShopWeb.Web.Home.HomePage.Template uses Microsoft.eShopWeb.Web.PublicLayout✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.HomePage.Template uses a type in Microsoft.eShopWeb.Web.PublicLayout.
- The types involved
Microsoft.eShopWeb.Web.Home.HomePage.Template.Template→Microsoft.eShopWeb.Web.PublicLayout.HeadMetadata
- Direction
- Microsoft.eShopWeb.Web.Home.HomePage.Template uses Microsoft.eShopWeb.Web.PublicLayout, so a change to Microsoft.eShopWeb.Web.PublicLayout can break Microsoft.eShopWeb.Web.Home.HomePage.Template, while a change to Microsoft.eShopWeb.Web.Home.HomePage.Template can't break Microsoft.eShopWeb.Web.PublicLayout.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.HomePage.Template uses a module listed above it, which is the healthy direction.
26→24 Microsoft.eShopWeb.Web.Home.HomePage.Template uses Microsoft.eShopWeb.Web.Home.HomePage✕
- Connections
- 1 pair of types, where a type in Microsoft.eShopWeb.Web.Home.HomePage.Template uses a type in Microsoft.eShopWeb.Web.Home.HomePage.
- The types involved
Microsoft.eShopWeb.Web.Home.HomePage.Template.Template→Microsoft.eShopWeb.Web.Home.HomePage.Props
- Direction
- Microsoft.eShopWeb.Web.Home.HomePage.Template uses Microsoft.eShopWeb.Web.Home.HomePage, so a change to Microsoft.eShopWeb.Web.Home.HomePage can break Microsoft.eShopWeb.Web.Home.HomePage.Template, while a change to Microsoft.eShopWeb.Web.Home.HomePage.Template can't break Microsoft.eShopWeb.Web.Home.HomePage.
- Position
- Below the diagonal: Microsoft.eShopWeb.Web.Home.HomePage.Template uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 16 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 13 Low coverage finding(s) in Code Coverage — start with Program.fs, Basket.Page.fs, Basket.Component.fs; Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 13 Low coverage finding(s) in Code Coverage — start with Program.fs, Basket.Page.fs, Basket.Component.fs. | +11.3 pts | Medium | Code Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.9 pts | Low | ADR Quality |
| Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with Login.Page.fs, Basket.Domain.fs, Persistence.fs. | +3.9 pts | Low | Knowledge Freshness |
| Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run. | +7.4 pts | Medium | Observability |
| Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). | +2.7 pts | Low | Dependency Hygiene |
| 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. | +3.0 pts | Medium | Visual & motion safety |
| 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. | +2.8 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.7 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 6.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs | 6.3 | Mixed | Code Duplication: Duplicated block (42–43 lines × 2) |
| src/Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs | 7.0 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| Directory.Packages.props | 7.8 | Mixed | Dependency Hygiene: Deprecated: xunit |
| src/Microsoft.eShopWeb.Web/Program.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Program.fs |
| src/Microsoft.eShopWeb.Web/Basket/Basket.Page.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Basket/Basket.Page.fs |
| src/Microsoft.eShopWeb.Web/Basket/Basket.Component.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Basket/Basket.Component.fs |
| src/Microsoft.eShopWeb.Web/Basket/Basket.Domain.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Basket/Basket.Domain.fs |
| src/Microsoft.eShopWeb.Web/Home/Home.Page.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Home/Home.Page.fs |
| src/Microsoft.eShopWeb.Web/Home/CatalogPager.Component.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Home/CatalogPager.Component.fs |
| src/Microsoft.eShopWeb.Web/Home/CatalogGrid.Component.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Home/CatalogGrid.Component.fs |
| src/Microsoft.eShopWeb.Web/Home/CatalogFilters.Component.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Home/CatalogFilters.Component.fs |
| src/Microsoft.eShopWeb.Web/Layout/Public.Layout.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Layout/Public.Layout.fs |
| src/Microsoft.eShopWeb.Web/Request.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Request.fs |
| src/Microsoft.eShopWeb.Web/Persistence.fs | 8.5 | Near-clean | Code Coverage: Low coverage: src/Microsoft.eShopWeb.Web/Persistence.fs |
| src/Microsoft.eShopWeb.Web/packages.lock.json | 9.5 | Near-clean | Dependency Hygiene: Deprecated: SQLitePCLRaw.lib.e_sqlite3 |
| Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs | 9.5 | Near-clean | IL Efficiency: IL efficiency: 1 authored method(s) exceed the IL budget |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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. 48 of 48 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. 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.
What we checked — 48 dimensions across the health lenses
- 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, 66 of 79 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- 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 8 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 8 of the 14 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- D19 Documentation 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Microsoft.Extensions.DependencyInjection registered from F#, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality 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.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
3 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (42–43 lines × 2) finding(s) in Code Duplication — start with Account.Layout.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with Account.Layout.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Login.Page.fs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D8 · Code Coverage
Line coverage 4.3% — 13 file(s) below 50%.
What to do
- Resolve the 13 Low coverage finding(s) in Code Coverage — start with Program.fs, Basket.Page.fs, Basket.Component.fs. — One of this dimension's main actionable groups (13 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
8 outdated, 0 vulnerable, 1 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 1 outdated of 2 package(s) across 1 lockfile(s).
What to do
- Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props (2). — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 143 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 8 direct `PackageReference`(s), and 135 further package(s) were reached beyond them by closing the graph over the committed `REDACTED` and 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
97 % of calls cross a namespace and 0 % go through an interface, but 97 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. 4 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.
What to do
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
16 finding(s): 0 critical, 13 high, 3 medium, 0 low.
What to do
- Resolve the 13 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED, REDACTED. — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
8 of 8 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs. Counted over 8 of the 14 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with Login.Page.fs, Basket.Domain.fs, Persistence.fs. — One of this dimension's main actionable groups (8 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D39 · IL Efficiency
1 of 176 first-party methods have an oversized IL body.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 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.
What to do
- 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).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
AC6 · Visual & motion safety
- `.esh-basketstatus-badge` sets color: #ffffff on background-color: #83d01b — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Microsoft.eShopWeb.Web/Layout/_basket.scss:17
- `.esh-basketstatus-badge-inoperative` sets color: #ffffff on background-color: #ff0000 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Microsoft.eShopWeb.Web/Layout/_basket.scss:31
- `.esh-catalog-send` sets color: #ffffff on background-color: #83d01b — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Microsoft.eShopWeb.Web/Home/_catalogFilters.scss:51
- `.esh-basket-checkout` sets color: #ffffff on background-color: #83d01b — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Microsoft.eShopWeb.Web/Home/_index.scss:51
- `.esh-catalog-button` sets color: #ffffff on background-color: #83d01b — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/Microsoft.eShopWeb.Web/Home/_productsGrid.scss:42
- `.esh-identity-drop` moves (`transition: height 0.35s`) 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/Microsoft.eShopWeb.Web/Layout/_identity.scss:41
- `.esh-identity:hover .esh-identity-drop` moves (`transition: height 0.35s`) 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/Microsoft.eShopWeb.Web/Layout/_identity.scss:47
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 enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 8 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. — REDACTED:19
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, 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.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 14 F# production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (F#: Microsoft.Extensions.Logging (ILogger), Serilog, NLog, log4net, Logary) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run.
- Consider OpenTelemetry tracing/metrics (OpenTelemetry.Extensions.Hosting with the ASP.NET Core instrumentation) and a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1449 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:11
- `Directory.Packages.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Directory.Packages.props:10
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- 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.
PF3 · Async & latency hygiene
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Solid. |
| Architecture | 78% | Strong | Solid. |
| Maturity | 55% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 38% | Weak — gated by D8, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Adequate — gated by D30 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 56% | Adequate — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence 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.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~168 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. 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"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 1 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (1 with fewer than two methods), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's F# code has 976 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 17 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 31 finding(s)
- Low coverage: src/Microsoft.eShopWeb.Web/Program.fs src/Microsoft.eShopWeb.Web/Program.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Basket/Basket.Page.fs src/Microsoft.eShopWeb.Web/Basket/Basket.Page.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Basket/Basket.Component.fs src/Microsoft.eShopWeb.Web/Basket/Basket.Component.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Basket/Basket.Domain.fs src/Microsoft.eShopWeb.Web/Basket/Basket.Domain.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Home/Home.Page.fs src/Microsoft.eShopWeb.Web/Home/Home.Page.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Home/CatalogPager.Component.fs src/Microsoft.eShopWeb.Web/Home/CatalogPager.Component.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Home/CatalogGrid.Component.fs src/Microsoft.eShopWeb.Web/Home/CatalogGrid.Component.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Home/CatalogFilters.Component.fs src/Microsoft.eShopWeb.Web/Home/CatalogFilters.Component.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs src/Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Layout/Public.Layout.fs src/Microsoft.eShopWeb.Web/Layout/Public.Layout.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Request.fs src/Microsoft.eShopWeb.Web/Request.fs:1
- Low coverage: src/Microsoft.eShopWeb.Web/Persistence.fs src/Microsoft.eShopWeb.Web/Persistence.fs:1
- Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Layout/_basket.scss:17
- Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Home/_catalogFilters.scss:51
- Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Home/_index.scss:51
- Low contrast colour pair in CSS (1.9:1) src/Microsoft.eShopWeb.Web/Home/_productsGrid.scss:42
- REDACTED
- REDACTED
- REDACTED
- Animation without a prefers-reduced-motion guard src/Microsoft.eShopWeb.Web/Layout/_identity.scss:41
- Animation without a prefers-reduced-motion guard src/Microsoft.eShopWeb.Web/Layout/_identity.scss:47
- Low contrast colour pair in CSS (4.0:1) src/Microsoft.eShopWeb.Web/Layout/_basket.scss:31
- Accessibility enforcement below the top rung REDACTED:19
- Deprecated: xunit Directory.Packages.props:17
- REDACTED
- Duplicated block (42–43 lines × 2) src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs:10
- Duplicated block (18 lines × 2) src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs:51
- Duplicated block (9 lines × 2) src/Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs:74
- End-of-life runtime: Node.js 16 REDACTED:11
- No structured logging
Minor — 24 finding(s)
- Orphaned file src/Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs:1
- Orphaned file src/Microsoft.eShopWeb.Web/Basket/Basket.Domain.fs:1
- Orphaned file src/Microsoft.eShopWeb.Web/Persistence.fs:1
- Orphaned file src/Microsoft.eShopWeb.Web/Layout/Public.Layout.fs:1
- Orphaned file src/Microsoft.eShopWeb.Web/Basket/Basket.Component.fs:1
- Orphaned file src/Microsoft.eShopWeb.Web/Basket/Basket.Page.fs:1
- Orphaned file src/Microsoft.eShopWeb.Web/Layout/Account.Layout.fs:1
- Orphaned file src/Microsoft.eShopWeb.Web/Program.fs:1
- Deprecated: SQLitePCLRaw.lib.e_sqlite3 src/Microsoft.eShopWeb.Web/packages.lock.json:205
- Deprecated: SQLitePCLRaw.lib.e_sqlite3 REDACTED:256
- Deprecated: xunit.assert REDACTED:289
- Deprecated: xunit.core REDACTED:294
- Deprecated: xunit.extensibility.core REDACTED:303
- Deprecated: xunit.extensibility.execution REDACTED:311
- Outdated: EntityFrameworkCore.FSharp Directory.Packages.props:10
- Outdated: coverlet.collector Directory.Packages.props:15
- No ADRs found
- Orphaned files with no living knowledge
- REDACTED
- IL efficiency: 1 authored method(s) exceed the IL budget Microsoft.eShopWeb.Web/Account/Login/Login.Page.fs:27
- No ADRs
- No SAST REDACTED:11
- No dependency-update automation Directory.Packages.props:10
- No changelog
Minor — 7 finding(s)
- Outdated: Falco
- Outdated: Microsoft.EntityFrameworkCore.Sqlite
- Outdated: Microsoft.EntityFrameworkCore.InMemory
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit
- Outdated: xunit.runner.visualstudio
- Outdated (npm): bootstrap
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f423835eaf584a0e9ded3faf9066d58d/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f423835eaf584a0e9ded3faf9066d58d/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/Microsoft.eShopWeb.Web/wwwroot/css . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Microsoft.FShopWeb.sln package --vulnerable --include-transitive --format json | 16 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | 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 Confinement | runtime-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 Confinement | runtime-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 Enforcement | runtime-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 Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |