Executive summary
slaveOftime/Fun.Blazor is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because we found no access checks on the code's endpoints or handlers. It scores 39 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 30, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 8 points. Pinning the third-party scripts comes next, worth about 7 points. Raising Security and Compliance to 70 would lift the score to about 47.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five known security holes in the packages the code depends on can be used by attackers, and one secret can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting the secret to its own step would close these risks. The image with no text description needs a text description.
The product code is 42,919 lines, about €35,000 to rebuild.
If Security and Compliance rose from 30 to 70, the lowest score rated Strong, the score would rise from 39 to about 47.
New since the last survey: 10 findings
- God Classes · TooManyMethods: FluentFieldBuilder`1 Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs
- God Classes · TooManyMethods: FluentButtonBuilder`1 Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs
- God Classes · TooManyMethods: RadzenInlineAIPromptBuilder`1 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs
- God Classes · TooManyMethods: RadzenChartBuilder`1 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) Fun.Blazor.Docs.Wasm/wwwroot/css/prism-vsc-dark-plus.css
Fixed since the last survey: 10 findings
- God Classes · TooManyMethods: FluentDesignSystemProviderBuilder`1 Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs
- God Classes · TooManyMethods: FluentProfileMenuBuilder`1 Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs
- God Classes · TooManyMethods: FluentAutocompleteBuilder`2 Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs
- God Classes · TooManyMethods: FluentPopoverBuilder`1 Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Supply-chain Provenance & Signing · REDACTED REDACTED
- Supply-chain Provenance & Signing · REDACTED REDACTED
- Supply-chain Provenance & Signing · REDACTED REDACTED
- Supply-chain Provenance & Signing · REDACTED REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €35,000 · Estimate
| Cost to rebuild | €12,000 to €58,000, for 192 to 608 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 39. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 42,919 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 FSharp.Compiler.PortaCode.CodeModel | 2 Fun.Blazor.Docs.Wasm | 3 Fun.Blazor.Internal | 4 Fun.Blazor | 5 AntDesign.DslInternals.Filters | 6 AntDesign.DslInternals.Internal | 7 AntDesign.DslInternals.Internal.ModalDialog | 8 AntDesign.DslInternals.Select | 9 AntDesign.DslInternals.statistic | 10 ApexCharts.DslInternals | 11 ApexCharts.DslInternals.Internal | 12 Blazor.Diagrams.DslInternals | 13 Blazor.Diagrams.DslInternals.Controls | 14 Blazor.Diagrams.DslInternals.Renderers | 15 Blazor.Diagrams.DslInternals.Widgets | 16 Fun.Htmx | 17 Microsoft.AspNetCore.Components.DslInternals | 18 MudBlazor.DslInternals | 19 Radzen.Blazor.DslInternals | 20 Radzen.Blazor.DslInternals.Blazor.Spreadsheet | 21 AntDesign.DslInternals | 22 AntDesign.Filters.DslCE | 23 AntDesign.Internal.DslCE | 24 AntDesign.Internal.ModalDialog.DslCE | 25 AntDesign.Select.DslCE | 26 AntDesign.statistic.DslCE | 27 ApexCharts.DslCE | 28 ApexCharts.Internal.DslCE | 29 Blazor.Diagrams.Controls.DslCE | 30 Blazor.Diagrams.DslCE | 31 Microsoft.AspNetCore.Components.DslInternals.Web | 32 MudBlazor.DslInternals.Charts | 33 Radzen.Blazor.DslInternals.Blazor | 34 Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools | 35 AntDesign.DslCE | 36 AntDesign.DslInternals.Core.Component.ResizeObserver | 37 AntDesign.DslInternals.Select.Internal | 38 Radzen.Blazor.DslInternals.Blazor.Rendering | 39 AntDesign.Core.Component.ResizeObserver.DslCE | 40 AntDesign.Select.Internal.DslCE |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 FSharp.Compiler.PortaCode.CodeModel | ||||||||||||||||||||||||||||||||||||||||
| 2 Fun.Blazor.Docs.Wasm | ||||||||||||||||||||||||||||||||||||||||
| 3 Fun.Blazor.Internal | 3 | |||||||||||||||||||||||||||||||||||||||
| 4 Fun.Blazor | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 AntDesign.DslInternals.Filters | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 AntDesign.DslInternals.Internal | 21 | 18 | ||||||||||||||||||||||||||||||||||||||
| 7 AntDesign.DslInternals.Internal.ModalDialog | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 AntDesign.DslInternals.Select | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 AntDesign.DslInternals.statistic | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 ApexCharts.DslInternals | 13 | |||||||||||||||||||||||||||||||||||||||
| 11 ApexCharts.DslInternals.Internal | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 Blazor.Diagrams.DslInternals | 15 | |||||||||||||||||||||||||||||||||||||||
| 13 Blazor.Diagrams.DslInternals.Controls | 10 | |||||||||||||||||||||||||||||||||||||||
| 14 Blazor.Diagrams.DslInternals.Renderers | 12 | |||||||||||||||||||||||||||||||||||||||
| 15 Blazor.Diagrams.DslInternals.Widgets | 6 | |||||||||||||||||||||||||||||||||||||||
| 16 Fun.Htmx | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 Microsoft.AspNetCore.Components.DslInternals | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 MudBlazor.DslInternals | 178 | |||||||||||||||||||||||||||||||||||||||
| 19 Radzen.Blazor.DslInternals | 11 | |||||||||||||||||||||||||||||||||||||||
| 20 Radzen.Blazor.DslInternals.Blazor.Spreadsheet | 66 | |||||||||||||||||||||||||||||||||||||||
| 21 AntDesign.DslInternals | 219 | 5 | ||||||||||||||||||||||||||||||||||||||
| 22 AntDesign.Filters.DslCE | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 AntDesign.Internal.DslCE | 21 | |||||||||||||||||||||||||||||||||||||||
| 24 AntDesign.Internal.ModalDialog.DslCE | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 AntDesign.Select.DslCE | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 AntDesign.statistic.DslCE | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 ApexCharts.DslCE | 10 | |||||||||||||||||||||||||||||||||||||||
| 28 ApexCharts.Internal.DslCE | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 Blazor.Diagrams.Controls.DslCE | 5 | |||||||||||||||||||||||||||||||||||||||
| 30 Blazor.Diagrams.DslCE | 7 | |||||||||||||||||||||||||||||||||||||||
| 31 Microsoft.AspNetCore.Components.DslInternals.Web | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 MudBlazor.DslInternals.Charts | 8 | 7 | ||||||||||||||||||||||||||||||||||||||
| 33 Radzen.Blazor.DslInternals.Blazor | 417 | 132 | ||||||||||||||||||||||||||||||||||||||
| 34 Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 AntDesign.DslCE | 192 | |||||||||||||||||||||||||||||||||||||||
| 36 AntDesign.DslInternals.Core.Component.ResizeObserver | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 AntDesign.DslInternals.Select.Internal | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 Radzen.Blazor.DslInternals.Blazor.Rendering | 85 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 39 AntDesign.Core.Component.ResizeObserver.DslCE | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 AntDesign.Select.Internal.DslCE | 3 |
3→4 Fun.Blazor.Internal uses Fun.Blazor part of a loop✕
- Connections
- 3 pairs of types, where a type in Fun.Blazor.Internal uses a type in Fun.Blazor.
- The types involved
Fun.Blazor.Internal.StyleBuilder→Fun.Blazor.AttrRenderFragmentFun.Blazor.Internal.StyleEltBuilder→Fun.Blazor.EltWithChildBuilderFun.Blazor.Internal.StyleEltBuilder→Fun.Blazor.NodeRenderFragment
- Direction
- Fun.Blazor.Internal uses Fun.Blazor, so a change to Fun.Blazor can break Fun.Blazor.Internal, while a change to Fun.Blazor.Internal can't break Fun.Blazor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→3 Fun.Blazor uses Fun.Blazor.Internal✕
- Connections
- 2 pairs of types, where a type in Fun.Blazor uses a type in Fun.Blazor.Internal.
- The types involved
Fun.Blazor.CssRules→Fun.Blazor.Internal.KeyFrameFun.Blazor.ICssRules→Fun.Blazor.Internal.KeyFrame
- Direction
- Fun.Blazor uses Fun.Blazor.Internal, so a change to Fun.Blazor.Internal can break Fun.Blazor, while a change to Fun.Blazor can't break Fun.Blazor.Internal.
- Position
- Below the diagonal: Fun.Blazor uses a module listed above it, which is the healthy direction.
5→4 AntDesign.DslInternals.Filters uses Fun.Blazor✕
- Connections
- 1 pair of types, where a type in AntDesign.DslInternals.Filters uses a type in Fun.Blazor.
- The types involved
AntDesign.DslInternals.Filters.FilterInputsBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- AntDesign.DslInternals.Filters uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals.Filters, while a change to AntDesign.DslInternals.Filters can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals.Filters uses a module listed above it, which is the healthy direction.
6→4 AntDesign.DslInternals.Internal uses Fun.Blazor✕
- Connections
- 21 pairs of types, where a type in AntDesign.DslInternals.Internal uses a type in Fun.Blazor.
- The types involved
AntDesign.DslInternals.Internal.CalendarPanelChooserBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DatePickerDatePanelBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DatePickerDatetimePanelBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DatePickerHeaderBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DatePickerInputBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DatePickerInputBuilder`1→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.Internal.DatePickerPanelChooserBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DatePickerTemplateBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DatePickerTemplateBuilder`2→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.Internal.DropdownGroupButtonBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.DropdownGroupButtonBuilder`1→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.Internal.ElementBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.FormRulesValidatorBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1AntDesign.DslInternals.Internal.OverlayBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.OverlayTriggerBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.OverlayTriggerBuilder`1→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.Internal.PickerPanelBaseBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.SubMenuTriggerBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.TableRowWrapperBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Internal.TableRowWrapperBuilder`2→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1AntDesign.DslInternals.Internal.UploadButtonBuilder`1→Fun.Blazor.AttrRenderFragment
- Direction
- AntDesign.DslInternals.Internal uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals.Internal, while a change to AntDesign.DslInternals.Internal can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals.Internal uses a module listed above it, which is the healthy direction.
6→21 AntDesign.DslInternals.Internal uses AntDesign.DslInternals part of a loop✕
- Connections
- 18 pairs of types, where a type in AntDesign.DslInternals.Internal uses a type in AntDesign.DslInternals.
- The types involved
AntDesign.DslInternals.Internal.CalendarPanelChooserBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.DatePickerDatePanelBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerDatetimePanelBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerDecadePanelBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerFooterBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerHeaderBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerInputBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.DatePickerMonthPanelBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerPanelChooserBuilder`2→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.DatePickerQuarterPanelBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerTemplateBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DatePickerYearPanelBuilder`2→AntDesign.DslInternals.DatePickerPanelBaseBuilder`2AntDesign.DslInternals.Internal.DropdownGroupButtonBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.ElementBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.OverlayBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.OverlayTriggerBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.PickerPanelBaseBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Internal.UploadButtonBuilder`1→AntDesign.DslInternals.AntDomComponentBaseBuilder`1
- Direction
- AntDesign.DslInternals.Internal uses AntDesign.DslInternals, so a change to AntDesign.DslInternals can break AntDesign.DslInternals.Internal, while a change to AntDesign.DslInternals.Internal can't break AntDesign.DslInternals.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→4 AntDesign.DslInternals.Internal.ModalDialog uses Fun.Blazor✕
- Connections
- 1 pair of types, where a type in AntDesign.DslInternals.Internal.ModalDialog uses a type in Fun.Blazor.
- The types involved
AntDesign.DslInternals.Internal.ModalDialog.ModalHeaderBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- AntDesign.DslInternals.Internal.ModalDialog uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals.Internal.ModalDialog, while a change to AntDesign.DslInternals.Internal.ModalDialog can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals.Internal.ModalDialog uses a module listed above it, which is the healthy direction.
8→4 AntDesign.DslInternals.Select uses Fun.Blazor✕
- Connections
- 2 pairs of types, where a type in AntDesign.DslInternals.Select uses a type in Fun.Blazor.
- The types involved
AntDesign.DslInternals.Select.LabelTemplateItemBuilder`3→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Select.LabelTemplateItemBuilder`3→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- AntDesign.DslInternals.Select uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals.Select, while a change to AntDesign.DslInternals.Select can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals.Select uses a module listed above it, which is the healthy direction.
9→4 AntDesign.DslInternals.statistic uses Fun.Blazor✕
- Connections
- 1 pair of types, where a type in AntDesign.DslInternals.statistic uses a type in Fun.Blazor.
- The types involved
AntDesign.DslInternals.statistic.StatisticComponentBaseBuilder`2→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- AntDesign.DslInternals.statistic uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals.statistic, while a change to AntDesign.DslInternals.statistic can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals.statistic uses a module listed above it, which is the healthy direction.
10→4 ApexCharts.DslInternals uses Fun.Blazor✕
- Connections
- 13 pairs of types, where a type in ApexCharts.DslInternals uses a type in Fun.Blazor.
- The types involved
ApexCharts.DslInternals.ApexBaseSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexBaseSeriesBuilder`2→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1ApexCharts.DslInternals.ApexBoxPlotSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexBubbleSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexCandleSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexChartBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexChartBuilder`2→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1ApexCharts.DslInternals.ApexGaugeBuilder`1→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexGaugeBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1ApexCharts.DslInternals.ApexPointSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexRangeAreaSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexRangeSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.ApexViolinSeriesBuilder`2→Fun.Blazor.AttrRenderFragment
- Direction
- ApexCharts.DslInternals uses Fun.Blazor, so a change to Fun.Blazor can break ApexCharts.DslInternals, while a change to ApexCharts.DslInternals can't break Fun.Blazor.
- Position
- Below the diagonal: ApexCharts.DslInternals uses a module listed above it, which is the healthy direction.
11→4 ApexCharts.DslInternals.Internal uses Fun.Blazor✕
- Connections
- 2 pairs of types, where a type in ApexCharts.DslInternals.Internal uses a type in Fun.Blazor.
- The types involved
ApexCharts.DslInternals.Internal.ApexChartTooltipBuilder`2→Fun.Blazor.AttrRenderFragmentApexCharts.DslInternals.Internal.ApexChartTooltipBuilder`2→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- ApexCharts.DslInternals.Internal uses Fun.Blazor, so a change to Fun.Blazor can break ApexCharts.DslInternals.Internal, while a change to ApexCharts.DslInternals.Internal can't break Fun.Blazor.
- Position
- Below the diagonal: ApexCharts.DslInternals.Internal uses a module listed above it, which is the healthy direction.
12→4 Blazor.Diagrams.DslInternals uses Fun.Blazor✕
- Connections
- 15 pairs of types, where a type in Blazor.Diagrams.DslInternals uses a type in Fun.Blazor.
- The types involved
Blazor.Diagrams.DslInternals.DefaultGroupWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.DefaultGroupWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.DefaultLinkLabelWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.DefaultLinkLabelWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.DiagramCanvasBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.DiagramCanvasBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.DiagramCanvasBuilder`1→Fun.Blazor.NodeRenderFragmentBlazor.Diagrams.DslInternals.GroupNodesBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.GroupNodesBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.LinkWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.LinkWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.NodeWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.NodeWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.SvgNodeWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.SvgNodeWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- Blazor.Diagrams.DslInternals uses Fun.Blazor, so a change to Fun.Blazor can break Blazor.Diagrams.DslInternals, while a change to Blazor.Diagrams.DslInternals can't break Fun.Blazor.
- Position
- Below the diagonal: Blazor.Diagrams.DslInternals uses a module listed above it, which is the healthy direction.
13→4 Blazor.Diagrams.DslInternals.Controls uses Fun.Blazor✕
- Connections
- 10 pairs of types, where a type in Blazor.Diagrams.DslInternals.Controls uses a type in Fun.Blazor.
- The types involved
Blazor.Diagrams.DslInternals.Controls.ArrowHeadControlWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Controls.ArrowHeadControlWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Controls.BoundaryControlWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Controls.BoundaryControlWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Controls.ControlsLayerRendererBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Controls.ControlsLayerRendererBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Controls.DragNewLinkControlWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Controls.DragNewLinkControlWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Controls.RemoveControlWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Controls.RemoveControlWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- Blazor.Diagrams.DslInternals.Controls uses Fun.Blazor, so a change to Fun.Blazor can break Blazor.Diagrams.DslInternals.Controls, while a change to Blazor.Diagrams.DslInternals.Controls can't break Fun.Blazor.
- Position
- Below the diagonal: Blazor.Diagrams.DslInternals.Controls uses a module listed above it, which is the healthy direction.
14→4 Blazor.Diagrams.DslInternals.Renderers uses Fun.Blazor✕
- Connections
- 12 pairs of types, where a type in Blazor.Diagrams.DslInternals.Renderers uses a type in Fun.Blazor.
- The types involved
Blazor.Diagrams.DslInternals.Renderers.GroupRendererBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Renderers.GroupRendererBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Renderers.LinkLabelRendererBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Renderers.LinkLabelRendererBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Renderers.LinkRendererBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Renderers.LinkRendererBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Renderers.LinkVertexRendererBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Renderers.LinkVertexRendererBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Renderers.NodeRendererBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Renderers.NodeRendererBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Renderers.PortRendererBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Renderers.PortRendererBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1
- Direction
- Blazor.Diagrams.DslInternals.Renderers uses Fun.Blazor, so a change to Fun.Blazor can break Blazor.Diagrams.DslInternals.Renderers, while a change to Blazor.Diagrams.DslInternals.Renderers can't break Fun.Blazor.
- Position
- Below the diagonal: Blazor.Diagrams.DslInternals.Renderers uses a module listed above it, which is the healthy direction.
15→4 Blazor.Diagrams.DslInternals.Widgets uses Fun.Blazor✕
- Connections
- 6 pairs of types, where a type in Blazor.Diagrams.DslInternals.Widgets uses a type in Fun.Blazor.
- The types involved
Blazor.Diagrams.DslInternals.Widgets.GridWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Widgets.GridWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Widgets.NavigatorWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Widgets.NavigatorWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Blazor.Diagrams.DslInternals.Widgets.SelectionBoxWidgetBuilder`1→Fun.Blazor.AttrRenderFragmentBlazor.Diagrams.DslInternals.Widgets.SelectionBoxWidgetBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- Blazor.Diagrams.DslInternals.Widgets uses Fun.Blazor, so a change to Fun.Blazor can break Blazor.Diagrams.DslInternals.Widgets, while a change to Blazor.Diagrams.DslInternals.Widgets can't break Fun.Blazor.
- Position
- Below the diagonal: Blazor.Diagrams.DslInternals.Widgets uses a module listed above it, which is the healthy direction.
16→4 Fun.Htmx uses Fun.Blazor✕
- Connections
- 3 pairs of types, where a type in Fun.Htmx uses a type in Fun.Blazor.
- The types involved
Fun.Htmx.EmptyComp→Fun.Blazor.FunComponentFun.Htmx.EmptyComp→Fun.Blazor.NodeRenderFragmentFun.Htmx.NativeJs→Fun.Blazor.QueryBuilder`1
- Direction
- Fun.Htmx uses Fun.Blazor, so a change to Fun.Blazor can break Fun.Htmx, while a change to Fun.Htmx can't break Fun.Blazor.
- Position
- Below the diagonal: Fun.Htmx uses a module listed above it, which is the healthy direction.
17→4 Microsoft.AspNetCore.Components.DslInternals uses Fun.Blazor✕
- Connections
- 2 pairs of types, where a type in Microsoft.AspNetCore.Components.DslInternals uses a type in Fun.Blazor.
- The types involved
Microsoft.AspNetCore.Components.DslInternals.ErrorBoundaryBaseBuilder`1→Fun.Blazor.AttrRenderFragmentMicrosoft.AspNetCore.Components.DslInternals.ErrorBoundaryBaseBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1
- Direction
- Microsoft.AspNetCore.Components.DslInternals uses Fun.Blazor, so a change to Fun.Blazor can break Microsoft.AspNetCore.Components.DslInternals, while a change to Microsoft.AspNetCore.Components.DslInternals can't break Fun.Blazor.
- Position
- Below the diagonal: Microsoft.AspNetCore.Components.DslInternals uses a module listed above it, which is the healthy direction.
18→4 MudBlazor.DslInternals uses Fun.Blazor✕
- Connections
- 178 pairs of types, where a type in MudBlazor.DslInternals uses a type in Fun.Blazor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
MudBlazor.DslInternals.BreadcrumbLinkBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.BreadcrumbLinkBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1MudBlazor.DslInternals.BreadcrumbSeparatorBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1MudBlazor.DslInternals.ColumnBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.ComponentBaseWithStateBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1MudBlazor.DslInternals.DataGridGroupRowBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.DataGridVirtualizeRowBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.FilterHeaderCellBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.FooterCellBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.HeaderCellBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.HierarchyColumnBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudAlertBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudAppBarBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudAutocompleteBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudAutocompleteBuilder`2→Fun.Blazor.NodeRenderFragmentMudBlazor.DslInternals.MudAvatarBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudAvatarGroupBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBadgeBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBaseBindableItemsControlBuilder`3→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBaseButtonBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBaseDatePickerBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBaseInputBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBaseItemsControlBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBooleanInputBuilder`2→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.MudBreadcrumbsBuilder`1→Fun.Blazor.AttrRenderFragment
- Direction
- MudBlazor.DslInternals uses Fun.Blazor, so a change to Fun.Blazor can break MudBlazor.DslInternals, while a change to MudBlazor.DslInternals can't break Fun.Blazor.
- Position
- Below the diagonal: MudBlazor.DslInternals uses a module listed above it, which is the healthy direction.
19→4 Radzen.Blazor.DslInternals uses Fun.Blazor✕
- Connections
- 11 pairs of types, where a type in Radzen.Blazor.DslInternals uses a type in Fun.Blazor.
- The types involved
Radzen.Blazor.DslInternals.DataBoundFormComponentBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.DataBoundFormComponentBuilder`2→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.DropDownBaseBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.DropDownBaseBuilder`2→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.FormComponentBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.FormComponentWithAutoCompleteBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.PagedDataBoundComponentBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.PagedDataBoundComponentBuilder`2→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.RadzenComponentBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.RadzenComponentBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.RadzenFlexComponentBuilder`1→Fun.Blazor.AttrRenderFragment
- Direction
- Radzen.Blazor.DslInternals uses Fun.Blazor, so a change to Fun.Blazor can break Radzen.Blazor.DslInternals, while a change to Radzen.Blazor.DslInternals can't break Fun.Blazor.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals uses a module listed above it, which is the healthy direction.
20→4 Radzen.Blazor.DslInternals.Blazor.Spreadsheet uses Fun.Blazor✕
- Connections
- 66 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor.Spreadsheet uses a type in Fun.Blazor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Radzen.Blazor.DslInternals.Blazor.Spreadsheet.AutofillOverlayBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.AutofillOverlayBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.CellBaseBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.CellBaseBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.CellEditorBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.CellEditorBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.CellMenuBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.CellMenuBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.CellMenuItemBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.CellMenuItemBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.CellSelectionBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.CellSelectionBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.CellViewBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.ColumnHeaderBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.CopyOverlayBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.CopyOverlayBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.CustomSortDialogBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.DrawingOverlayBaseBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.DrawingOverlayBaseBuilder`2→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.DrawingSizeDialogBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.DrawingSizeDialogBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.EditChartDialogBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.FilterDialogBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.FormatCellsDialogBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.FormulaEditorBuilder`1→Fun.Blazor.AttrRenderFragment
- Direction
- Radzen.Blazor.DslInternals.Blazor.Spreadsheet uses Fun.Blazor, so a change to Fun.Blazor can break Radzen.Blazor.DslInternals.Blazor.Spreadsheet, while a change to Radzen.Blazor.DslInternals.Blazor.Spreadsheet can't break Fun.Blazor.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor.Spreadsheet uses a module listed above it, which is the healthy direction.
21→4 AntDesign.DslInternals uses Fun.Blazor✕
- Connections
- 219 pairs of types, where a type in AntDesign.DslInternals uses a type in Fun.Blazor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
AntDesign.DslInternals.ActionColumnBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AffixBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AlertBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AlertBuilder`1→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.AnchorBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AnchorLinkBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AntComponentBaseBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AntComponentBaseBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1AntDesign.DslInternals.AntContainerComponentBaseBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AntDomComponentBaseBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AntInputBoolComponentBaseBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AntInputComponentBaseBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AntListBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AntListBuilder`2→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.AutoCompleteBuilder`2→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AutoCompleteBuilder`2→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.AutoCompleteOptGroupBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AutoCompleteOptGroupBuilder`1→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.AutoCompleteOptionBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AvatarBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.AvatarGroupBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.BackTopBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.BadgeBuilder`1→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.BadgeBuilder`1→Fun.Blazor.NodeRenderFragmentAntDesign.DslInternals.BadgeRibbonBuilder`1→Fun.Blazor.AttrRenderFragment
- Direction
- AntDesign.DslInternals uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals, while a change to AntDesign.DslInternals can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals uses a module listed above it, which is the healthy direction.
21→6 AntDesign.DslInternals uses AntDesign.DslInternals.Internal✕
- Connections
- 5 pairs of types, where a type in AntDesign.DslInternals uses a type in AntDesign.DslInternals.Internal.
- The types involved
AntDesign.DslInternals.DatePickerPanelBaseBuilder`2→AntDesign.DslInternals.Internal.PickerPanelBaseBuilder`1AntDesign.DslInternals.DropdownBuilder`1→AntDesign.DslInternals.Internal.OverlayTriggerBuilder`1AntDesign.DslInternals.PopconfirmBuilder`1→AntDesign.DslInternals.Internal.OverlayTriggerBuilder`1AntDesign.DslInternals.PopoverBuilder`1→AntDesign.DslInternals.Internal.OverlayTriggerBuilder`1AntDesign.DslInternals.TooltipBuilder`1→AntDesign.DslInternals.Internal.OverlayTriggerBuilder`1
- Direction
- AntDesign.DslInternals uses AntDesign.DslInternals.Internal, so a change to AntDesign.DslInternals.Internal can break AntDesign.DslInternals, while a change to AntDesign.DslInternals can't break AntDesign.DslInternals.Internal.
- Position
- Below the diagonal: AntDesign.DslInternals uses a module listed above it, which is the healthy direction.
22→5 AntDesign.Filters.DslCE uses AntDesign.DslInternals.Filters✕
- Connections
- 1 pair of types, where a type in AntDesign.Filters.DslCE uses a type in AntDesign.DslInternals.Filters.
- The types involved
AntDesign.Filters.DslCE.FilterInputs'→AntDesign.DslInternals.Filters.FilterInputsBuilder`1
- Direction
- AntDesign.Filters.DslCE uses AntDesign.DslInternals.Filters, so a change to AntDesign.DslInternals.Filters can break AntDesign.Filters.DslCE, while a change to AntDesign.Filters.DslCE can't break AntDesign.DslInternals.Filters.
- Position
- Below the diagonal: AntDesign.Filters.DslCE uses a module listed above it, which is the healthy direction.
23→6 AntDesign.Internal.DslCE uses AntDesign.DslInternals.Internal✕
- Connections
- 21 pairs of types, where a type in AntDesign.Internal.DslCE uses a type in AntDesign.DslInternals.Internal.
- The types involved
AntDesign.Internal.DslCE.CalendarPanelChooser'→AntDesign.DslInternals.Internal.CalendarPanelChooserBuilder`1AntDesign.Internal.DslCE.DatePickerDatePanel'`1→AntDesign.DslInternals.Internal.DatePickerDatePanelBuilder`2AntDesign.Internal.DslCE.DatePickerDatetimePanel'`1→AntDesign.DslInternals.Internal.DatePickerDatetimePanelBuilder`2AntDesign.Internal.DslCE.DatePickerDecadePanel'`1→AntDesign.DslInternals.Internal.DatePickerDecadePanelBuilder`2AntDesign.Internal.DslCE.DatePickerFooter'`1→AntDesign.DslInternals.Internal.DatePickerFooterBuilder`2AntDesign.Internal.DslCE.DatePickerHeader'`1→AntDesign.DslInternals.Internal.DatePickerHeaderBuilder`2AntDesign.Internal.DslCE.DatePickerInput'→AntDesign.DslInternals.Internal.DatePickerInputBuilder`1AntDesign.Internal.DslCE.DatePickerMonthPanel'`1→AntDesign.DslInternals.Internal.DatePickerMonthPanelBuilder`2AntDesign.Internal.DslCE.DatePickerPanelChooser'`1→AntDesign.DslInternals.Internal.DatePickerPanelChooserBuilder`2AntDesign.Internal.DslCE.DatePickerQuarterPanel'`1→AntDesign.DslInternals.Internal.DatePickerQuarterPanelBuilder`2AntDesign.Internal.DslCE.DatePickerTemplate'`1→AntDesign.DslInternals.Internal.DatePickerTemplateBuilder`2AntDesign.Internal.DslCE.DatePickerYearPanel'`1→AntDesign.DslInternals.Internal.DatePickerYearPanelBuilder`2AntDesign.Internal.DslCE.DropdownGroupButton'→AntDesign.DslInternals.Internal.DropdownGroupButtonBuilder`1AntDesign.Internal.DslCE.Element'→AntDesign.DslInternals.Internal.ElementBuilder`1AntDesign.Internal.DslCE.FormRulesValidator'→AntDesign.DslInternals.Internal.FormRulesValidatorBuilder`1AntDesign.Internal.DslCE.Overlay'→AntDesign.DslInternals.Internal.OverlayBuilder`1AntDesign.Internal.DslCE.OverlayTrigger'→AntDesign.DslInternals.Internal.OverlayTriggerBuilder`1AntDesign.Internal.DslCE.PickerPanelBase'→AntDesign.DslInternals.Internal.PickerPanelBaseBuilder`1AntDesign.Internal.DslCE.SubMenuTrigger'→AntDesign.DslInternals.Internal.SubMenuTriggerBuilder`1AntDesign.Internal.DslCE.TableRowWrapper'`1→AntDesign.DslInternals.Internal.TableRowWrapperBuilder`2AntDesign.Internal.DslCE.UploadButton'→AntDesign.DslInternals.Internal.UploadButtonBuilder`1
- Direction
- AntDesign.Internal.DslCE uses AntDesign.DslInternals.Internal, so a change to AntDesign.DslInternals.Internal can break AntDesign.Internal.DslCE, while a change to AntDesign.Internal.DslCE can't break AntDesign.DslInternals.Internal.
- Position
- Below the diagonal: AntDesign.Internal.DslCE uses a module listed above it, which is the healthy direction.
24→7 AntDesign.Internal.ModalDialog.DslCE uses AntDesign.DslInternals.Internal.ModalDialog✕
- Connections
- 1 pair of types, where a type in AntDesign.Internal.ModalDialog.DslCE uses a type in AntDesign.DslInternals.Internal.ModalDialog.
- The types involved
AntDesign.Internal.ModalDialog.DslCE.ModalHeader'→AntDesign.DslInternals.Internal.ModalDialog.ModalHeaderBuilder`1
- Direction
- AntDesign.Internal.ModalDialog.DslCE uses AntDesign.DslInternals.Internal.ModalDialog, so a change to AntDesign.DslInternals.Internal.ModalDialog can break AntDesign.Internal.ModalDialog.DslCE, while a change to AntDesign.Internal.ModalDialog.DslCE can't break AntDesign.DslInternals.Internal.ModalDialog.
- Position
- Below the diagonal: AntDesign.Internal.ModalDialog.DslCE uses a module listed above it, which is the healthy direction.
25→8 AntDesign.Select.DslCE uses AntDesign.DslInternals.Select✕
- Connections
- 1 pair of types, where a type in AntDesign.Select.DslCE uses a type in AntDesign.DslInternals.Select.
- The types involved
AntDesign.Select.DslCE.LabelTemplateItem'`2→AntDesign.DslInternals.Select.LabelTemplateItemBuilder`3
- Direction
- AntDesign.Select.DslCE uses AntDesign.DslInternals.Select, so a change to AntDesign.DslInternals.Select can break AntDesign.Select.DslCE, while a change to AntDesign.Select.DslCE can't break AntDesign.DslInternals.Select.
- Position
- Below the diagonal: AntDesign.Select.DslCE uses a module listed above it, which is the healthy direction.
26→9 AntDesign.statistic.DslCE uses AntDesign.DslInternals.statistic✕
- Connections
- 1 pair of types, where a type in AntDesign.statistic.DslCE uses a type in AntDesign.DslInternals.statistic.
- The types involved
AntDesign.statistic.DslCE.StatisticComponentBase'`1→AntDesign.DslInternals.statistic.StatisticComponentBaseBuilder`2
- Direction
- AntDesign.statistic.DslCE uses AntDesign.DslInternals.statistic, so a change to AntDesign.DslInternals.statistic can break AntDesign.statistic.DslCE, while a change to AntDesign.statistic.DslCE can't break AntDesign.DslInternals.statistic.
- Position
- Below the diagonal: AntDesign.statistic.DslCE uses a module listed above it, which is the healthy direction.
27→10 ApexCharts.DslCE uses ApexCharts.DslInternals✕
- Connections
- 10 pairs of types, where a type in ApexCharts.DslCE uses a type in ApexCharts.DslInternals.
- The types involved
ApexCharts.DslCE.ApexBaseSeries'`1→ApexCharts.DslInternals.ApexBaseSeriesBuilder`2ApexCharts.DslCE.ApexBoxPlotSeries'`1→ApexCharts.DslInternals.ApexBoxPlotSeriesBuilder`2ApexCharts.DslCE.ApexBubbleSeries'`1→ApexCharts.DslInternals.ApexBubbleSeriesBuilder`2ApexCharts.DslCE.ApexCandleSeries'`1→ApexCharts.DslInternals.ApexCandleSeriesBuilder`2ApexCharts.DslCE.ApexChart'`1→ApexCharts.DslInternals.ApexChartBuilder`2ApexCharts.DslCE.ApexGauge'→ApexCharts.DslInternals.ApexGaugeBuilder`1ApexCharts.DslCE.ApexPointSeries'`1→ApexCharts.DslInternals.ApexPointSeriesBuilder`2ApexCharts.DslCE.ApexRangeAreaSeries'`1→ApexCharts.DslInternals.ApexRangeAreaSeriesBuilder`2ApexCharts.DslCE.ApexRangeSeries'`1→ApexCharts.DslInternals.ApexRangeSeriesBuilder`2ApexCharts.DslCE.ApexViolinSeries'`1→ApexCharts.DslInternals.ApexViolinSeriesBuilder`2
- Direction
- ApexCharts.DslCE uses ApexCharts.DslInternals, so a change to ApexCharts.DslInternals can break ApexCharts.DslCE, while a change to ApexCharts.DslCE can't break ApexCharts.DslInternals.
- Position
- Below the diagonal: ApexCharts.DslCE uses a module listed above it, which is the healthy direction.
28→11 ApexCharts.Internal.DslCE uses ApexCharts.DslInternals.Internal✕
- Connections
- 1 pair of types, where a type in ApexCharts.Internal.DslCE uses a type in ApexCharts.DslInternals.Internal.
- The types involved
ApexCharts.Internal.DslCE.ApexChartTooltip'`1→ApexCharts.DslInternals.Internal.ApexChartTooltipBuilder`2
- Direction
- ApexCharts.Internal.DslCE uses ApexCharts.DslInternals.Internal, so a change to ApexCharts.DslInternals.Internal can break ApexCharts.Internal.DslCE, while a change to ApexCharts.Internal.DslCE can't break ApexCharts.DslInternals.Internal.
- Position
- Below the diagonal: ApexCharts.Internal.DslCE uses a module listed above it, which is the healthy direction.
29→13 Blazor.Diagrams.Controls.DslCE uses Blazor.Diagrams.DslInternals.Controls✕
- Connections
- 5 pairs of types, where a type in Blazor.Diagrams.Controls.DslCE uses a type in Blazor.Diagrams.DslInternals.Controls.
- The types involved
Blazor.Diagrams.Controls.DslCE.ArrowHeadControlWidget'→Blazor.Diagrams.DslInternals.Controls.ArrowHeadControlWidgetBuilder`1Blazor.Diagrams.Controls.DslCE.BoundaryControlWidget'→Blazor.Diagrams.DslInternals.Controls.BoundaryControlWidgetBuilder`1Blazor.Diagrams.Controls.DslCE.ControlsLayerRenderer'→Blazor.Diagrams.DslInternals.Controls.ControlsLayerRendererBuilder`1Blazor.Diagrams.Controls.DslCE.DragNewLinkControlWidget'→Blazor.Diagrams.DslInternals.Controls.DragNewLinkControlWidgetBuilder`1Blazor.Diagrams.Controls.DslCE.RemoveControlWidget'→Blazor.Diagrams.DslInternals.Controls.RemoveControlWidgetBuilder`1
- Direction
- Blazor.Diagrams.Controls.DslCE uses Blazor.Diagrams.DslInternals.Controls, so a change to Blazor.Diagrams.DslInternals.Controls can break Blazor.Diagrams.Controls.DslCE, while a change to Blazor.Diagrams.Controls.DslCE can't break Blazor.Diagrams.DslInternals.Controls.
- Position
- Below the diagonal: Blazor.Diagrams.Controls.DslCE uses a module listed above it, which is the healthy direction.
30→12 Blazor.Diagrams.DslCE uses Blazor.Diagrams.DslInternals✕
- Connections
- 7 pairs of types, where a type in Blazor.Diagrams.DslCE uses a type in Blazor.Diagrams.DslInternals.
- The types involved
Blazor.Diagrams.DslCE.DefaultGroupWidget'→Blazor.Diagrams.DslInternals.DefaultGroupWidgetBuilder`1Blazor.Diagrams.DslCE.DefaultLinkLabelWidget'→Blazor.Diagrams.DslInternals.DefaultLinkLabelWidgetBuilder`1Blazor.Diagrams.DslCE.DiagramCanvas'→Blazor.Diagrams.DslInternals.DiagramCanvasBuilder`1Blazor.Diagrams.DslCE.GroupNodes'→Blazor.Diagrams.DslInternals.GroupNodesBuilder`1Blazor.Diagrams.DslCE.LinkWidget'→Blazor.Diagrams.DslInternals.LinkWidgetBuilder`1Blazor.Diagrams.DslCE.NodeWidget'→Blazor.Diagrams.DslInternals.NodeWidgetBuilder`1Blazor.Diagrams.DslCE.SvgNodeWidget'→Blazor.Diagrams.DslInternals.SvgNodeWidgetBuilder`1
- Direction
- Blazor.Diagrams.DslCE uses Blazor.Diagrams.DslInternals, so a change to Blazor.Diagrams.DslInternals can break Blazor.Diagrams.DslCE, while a change to Blazor.Diagrams.DslCE can't break Blazor.Diagrams.DslInternals.
- Position
- Below the diagonal: Blazor.Diagrams.DslCE uses a module listed above it, which is the healthy direction.
31→4 Microsoft.AspNetCore.Components.DslInternals.Web uses Fun.Blazor✕
- Connections
- 3 pairs of types, where a type in Microsoft.AspNetCore.Components.DslInternals.Web uses a type in Fun.Blazor.
- The types involved
Microsoft.AspNetCore.Components.DslInternals.Web.HeadContentBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Microsoft.AspNetCore.Components.DslInternals.Web.HeadOutletBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Microsoft.AspNetCore.Components.DslInternals.Web.PageTitleBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1
- Direction
- Microsoft.AspNetCore.Components.DslInternals.Web uses Fun.Blazor, so a change to Fun.Blazor can break Microsoft.AspNetCore.Components.DslInternals.Web, while a change to Microsoft.AspNetCore.Components.DslInternals.Web can't break Fun.Blazor.
- Position
- Below the diagonal: Microsoft.AspNetCore.Components.DslInternals.Web uses a module listed above it, which is the healthy direction.
31→17 Microsoft.AspNetCore.Components.DslInternals.Web uses Microsoft.AspNetCore.Components.DslInternals✕
- Connections
- 1 pair of types, where a type in Microsoft.AspNetCore.Components.DslInternals.Web uses a type in Microsoft.AspNetCore.Components.DslInternals.
- The types involved
Microsoft.AspNetCore.Components.DslInternals.Web.ErrorBoundaryBuilder`1→Microsoft.AspNetCore.Components.DslInternals.ErrorBoundaryBaseBuilder`1
- Direction
- Microsoft.AspNetCore.Components.DslInternals.Web uses Microsoft.AspNetCore.Components.DslInternals, so a change to Microsoft.AspNetCore.Components.DslInternals can break Microsoft.AspNetCore.Components.DslInternals.Web, while a change to Microsoft.AspNetCore.Components.DslInternals.Web can't break Microsoft.AspNetCore.Components.DslInternals.
- Position
- Below the diagonal: Microsoft.AspNetCore.Components.DslInternals.Web uses a module listed above it, which is the healthy direction.
32→4 MudBlazor.DslInternals.Charts uses Fun.Blazor✕
- Connections
- 8 pairs of types, where a type in MudBlazor.DslInternals.Charts uses a type in Fun.Blazor.
- The types involved
MudBlazor.DslInternals.Charts.BaseAxisChartBuilder`3→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.Charts.BaseAxisChartBuilder`3→Fun.Blazor.NodeRenderFragmentMudBlazor.DslInternals.Charts.BaseRadialChartBuilder`3→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.Charts.BaseRadialChartBuilder`3→Fun.Blazor.NodeRenderFragmentMudBlazor.DslInternals.Charts.ChartTooltipBuilder`1→Fun.Blazor.AttrRenderFragmentMudBlazor.DslInternals.Charts.ChartTooltipBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1MudBlazor.DslInternals.Charts.FiltersBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1MudBlazor.DslInternals.Charts.LegendBuilder`2→Fun.Blazor.AttrRenderFragment
- Direction
- MudBlazor.DslInternals.Charts uses Fun.Blazor, so a change to Fun.Blazor can break MudBlazor.DslInternals.Charts, while a change to MudBlazor.DslInternals.Charts can't break Fun.Blazor.
- Position
- Below the diagonal: MudBlazor.DslInternals.Charts uses a module listed above it, which is the healthy direction.
32→18 MudBlazor.DslInternals.Charts uses MudBlazor.DslInternals✕
- Connections
- 7 pairs of types, where a type in MudBlazor.DslInternals.Charts uses a type in MudBlazor.DslInternals.
- The types involved
MudBlazor.DslInternals.Charts.BaseAxisChartBuilder`3→MudBlazor.DslInternals.MudComponentBaseBuilder`1MudBlazor.DslInternals.Charts.BaseRadialChartBuilder`3→MudBlazor.DslInternals.MudComponentBaseBuilder`1MudBlazor.DslInternals.Charts.HeatMapBuilder`2→MudBlazor.DslInternals.MudChartBaseBuilder`3MudBlazor.DslInternals.Charts.LegendBuilder`2→MudBlazor.DslInternals.MudChartBaseBuilder`3MudBlazor.DslInternals.Charts.MudAxisChartBaseBuilder`3→MudBlazor.DslInternals.MudChartBaseBuilder`3MudBlazor.DslInternals.Charts.MudRadialChartBaseBuilder`3→MudBlazor.DslInternals.MudChartBaseBuilder`3MudBlazor.DslInternals.Charts.SankeyBuilder`2→MudBlazor.DslInternals.MudChartBaseBuilder`3
- Direction
- MudBlazor.DslInternals.Charts uses MudBlazor.DslInternals, so a change to MudBlazor.DslInternals can break MudBlazor.DslInternals.Charts, while a change to MudBlazor.DslInternals.Charts can't break MudBlazor.DslInternals.
- Position
- Below the diagonal: MudBlazor.DslInternals.Charts uses a module listed above it, which is the healthy direction.
33→4 Radzen.Blazor.DslInternals.Blazor uses Fun.Blazor✕
- Connections
- 417 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor uses a type in Fun.Blazor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Radzen.Blazor.DslInternals.Blazor.AxisBaseBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.CartesianSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAIChatBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAIChatBuilder`1→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAIPromptBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAccordionBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAccordionBuilder`1→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAccordionItemBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAccordionItemBuilder`1→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAgendaViewBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAlertBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAppearanceToggleBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenArcGaugeScaleBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenArcGaugeScaleBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenArcGaugeScaleValueBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenArcGaugeScaleValueBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAreaSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAutoCompleteBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAutoCompleteBuilder`1→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAxisCrosshairBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenAxisTitleBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenBadgeBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenBarOptionsBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenBarSeriesBuilder`2→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.RadzenBarcodeBuilder`1→Fun.Blazor.AttrRenderFragment
- Direction
- Radzen.Blazor.DslInternals.Blazor uses Fun.Blazor, so a change to Fun.Blazor can break Radzen.Blazor.DslInternals.Blazor, while a change to Radzen.Blazor.DslInternals.Blazor can't break Fun.Blazor.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor uses a module listed above it, which is the healthy direction.
33→19 Radzen.Blazor.DslInternals.Blazor uses Radzen.Blazor.DslInternals✕
- Connections
- 132 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor uses a type in Radzen.Blazor.DslInternals. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Radzen.Blazor.DslInternals.Blazor.GaugeBaseBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAIChatBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAIPromptBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAccordionBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAccordionItemBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAlertBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentWithChildrenBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAppearanceToggleBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenAutoCompleteBuilder`1→Radzen.Blazor.DslInternals.DataBoundFormComponentBuilder`2Radzen.Blazor.DslInternals.Blazor.RadzenBadgeBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenBarcodeBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenBodyBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentWithChildrenBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenBreadCrumbBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentWithChildrenBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenBreadCrumbItemBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenButtonBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenCardBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentWithChildrenBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenCardGroupBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentWithChildrenBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenCarouselBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenChartBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenChatBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenCheckBoxBuilder`2→Radzen.Blazor.DslInternals.FormComponentBuilder`2Radzen.Blazor.DslInternals.Blazor.RadzenCheckBoxListBuilder`2→Radzen.Blazor.DslInternals.FormComponentBuilder`2Radzen.Blazor.DslInternals.Blazor.RadzenCheckBoxListItemBuilder`2→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenChipBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenChipItemBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.RadzenChipListBuilder`2→Radzen.Blazor.DslInternals.FormComponentBuilder`2
- Direction
- Radzen.Blazor.DslInternals.Blazor uses Radzen.Blazor.DslInternals, so a change to Radzen.Blazor.DslInternals can break Radzen.Blazor.DslInternals.Blazor, while a change to Radzen.Blazor.DslInternals.Blazor can't break Radzen.Blazor.DslInternals.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor uses a module listed above it, which is the healthy direction.
34→4 Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses Fun.Blazor✕
- Connections
- 3 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses a type in Fun.Blazor.
- The types involved
Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools.ConditionalFormatDialogBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools.HyperlinkDialogBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools.HyperlinkDialogBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses Fun.Blazor, so a change to Fun.Blazor can break Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools, while a change to Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools can't break Fun.Blazor.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses a module listed above it, which is the healthy direction.
34→20 Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses Radzen.Blazor.DslInternals.Blazor.Spreadsheet✕
- Connections
- 2 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses a type in Radzen.Blazor.DslInternals.Blazor.Spreadsheet.
- The types involved
Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools.ConditionalFormatDialogBuilder`1→Radzen.Blazor.DslInternals.Blazor.Spreadsheet.SpreadsheetDialogBaseBuilder`1Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools.DataValidationDialogBuilder`1→Radzen.Blazor.DslInternals.Blazor.Spreadsheet.SpreadsheetDialogBaseBuilder`1
- Direction
- Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses Radzen.Blazor.DslInternals.Blazor.Spreadsheet, so a change to Radzen.Blazor.DslInternals.Blazor.Spreadsheet can break Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools, while a change to Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools can't break Radzen.Blazor.DslInternals.Blazor.Spreadsheet.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor.Spreadsheet.Tools uses a module listed above it, which is the healthy direction.
35→21 AntDesign.DslCE uses AntDesign.DslInternals✕
- Connections
- 192 pairs of types, where a type in AntDesign.DslCE uses a type in AntDesign.DslInternals. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
AntDesign.DslCE.ActionColumn'→AntDesign.DslInternals.ActionColumnBuilder`1AntDesign.DslCE.Affix'→AntDesign.DslInternals.AffixBuilder`1AntDesign.DslCE.Alert'→AntDesign.DslInternals.AlertBuilder`1AntDesign.DslCE.Anchor'→AntDesign.DslInternals.AnchorBuilder`1AntDesign.DslCE.AnchorLink'→AntDesign.DslInternals.AnchorLinkBuilder`1AntDesign.DslCE.AntComponentBase'→AntDesign.DslInternals.AntComponentBaseBuilder`1AntDesign.DslCE.AntContainer'→AntDesign.DslInternals.AntContainerBuilder`1AntDesign.DslCE.AntContainerComponentBase'→AntDesign.DslInternals.AntContainerComponentBaseBuilder`1AntDesign.DslCE.AntDomComponentBase'→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslCE.AntInputBoolComponentBase'→AntDesign.DslInternals.AntInputBoolComponentBaseBuilder`1AntDesign.DslCE.AntInputComponentBase'`1→AntDesign.DslInternals.AntInputComponentBaseBuilder`2AntDesign.DslCE.AntList'`1→AntDesign.DslInternals.AntListBuilder`2AntDesign.DslCE.AutoComplete'`1→AntDesign.DslInternals.AutoCompleteBuilder`2AntDesign.DslCE.AutoCompleteInput'`1→AntDesign.DslInternals.AutoCompleteInputBuilder`2AntDesign.DslCE.AutoCompleteOptGroup'→AntDesign.DslInternals.AutoCompleteOptGroupBuilder`1AntDesign.DslCE.AutoCompleteOption'→AntDesign.DslInternals.AutoCompleteOptionBuilder`1AntDesign.DslCE.AutoCompleteSearch'→AntDesign.DslInternals.AutoCompleteSearchBuilder`1AntDesign.DslCE.Avatar'→AntDesign.DslInternals.AvatarBuilder`1AntDesign.DslCE.AvatarGroup'→AntDesign.DslInternals.AvatarGroupBuilder`1AntDesign.DslCE.BackTop'→AntDesign.DslInternals.BackTopBuilder`1AntDesign.DslCE.Badge'→AntDesign.DslInternals.BadgeBuilder`1AntDesign.DslCE.BadgeRibbon'→AntDesign.DslInternals.BadgeRibbonBuilder`1AntDesign.DslCE.Breadcrumb'→AntDesign.DslInternals.BreadcrumbBuilder`1AntDesign.DslCE.BreadcrumbItem'→AntDesign.DslInternals.BreadcrumbItemBuilder`1AntDesign.DslCE.Button'→AntDesign.DslInternals.ButtonBuilder`1
- Direction
- AntDesign.DslCE uses AntDesign.DslInternals, so a change to AntDesign.DslInternals can break AntDesign.DslCE, while a change to AntDesign.DslCE can't break AntDesign.DslInternals.
- Position
- Below the diagonal: AntDesign.DslCE uses a module listed above it, which is the healthy direction.
36→4 AntDesign.DslInternals.Core.Component.ResizeObserver uses Fun.Blazor✕
- Connections
- 1 pair of types, where a type in AntDesign.DslInternals.Core.Component.ResizeObserver uses a type in Fun.Blazor.
- The types involved
AntDesign.DslInternals.Core.Component.ResizeObserver.ResizeObserverBuilder`1→Fun.Blazor.AttrRenderFragment
- Direction
- AntDesign.DslInternals.Core.Component.ResizeObserver uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals.Core.Component.ResizeObserver, while a change to AntDesign.DslInternals.Core.Component.ResizeObserver can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals.Core.Component.ResizeObserver uses a module listed above it, which is the healthy direction.
36→21 AntDesign.DslInternals.Core.Component.ResizeObserver uses AntDesign.DslInternals✕
- Connections
- 1 pair of types, where a type in AntDesign.DslInternals.Core.Component.ResizeObserver uses a type in AntDesign.DslInternals.
- The types involved
AntDesign.DslInternals.Core.Component.ResizeObserver.ResizeObserverBuilder`1→AntDesign.DslInternals.AntComponentBaseBuilder`1
- Direction
- AntDesign.DslInternals.Core.Component.ResizeObserver uses AntDesign.DslInternals, so a change to AntDesign.DslInternals can break AntDesign.DslInternals.Core.Component.ResizeObserver, while a change to AntDesign.DslInternals.Core.Component.ResizeObserver can't break AntDesign.DslInternals.
- Position
- Below the diagonal: AntDesign.DslInternals.Core.Component.ResizeObserver uses a module listed above it, which is the healthy direction.
37→4 AntDesign.DslInternals.Select.Internal uses Fun.Blazor✕
- Connections
- 3 pairs of types, where a type in AntDesign.DslInternals.Select.Internal uses a type in Fun.Blazor.
- The types involved
AntDesign.DslInternals.Select.Internal.SelectContentBuilder`3→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Select.Internal.SelectSuffixIconBuilder`3→Fun.Blazor.AttrRenderFragmentAntDesign.DslInternals.Select.Internal.SelectSuffixIconBuilder`3→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- AntDesign.DslInternals.Select.Internal uses Fun.Blazor, so a change to Fun.Blazor can break AntDesign.DslInternals.Select.Internal, while a change to AntDesign.DslInternals.Select.Internal can't break Fun.Blazor.
- Position
- Below the diagonal: AntDesign.DslInternals.Select.Internal uses a module listed above it, which is the healthy direction.
37→21 AntDesign.DslInternals.Select.Internal uses AntDesign.DslInternals✕
- Connections
- 2 pairs of types, where a type in AntDesign.DslInternals.Select.Internal uses a type in AntDesign.DslInternals.
- The types involved
AntDesign.DslInternals.Select.Internal.SelectContentBuilder`3→AntDesign.DslInternals.AntDomComponentBaseBuilder`1AntDesign.DslInternals.Select.Internal.SelectOptionGroupBuilder`3→AntDesign.DslInternals.AntDomComponentBaseBuilder`1
- Direction
- AntDesign.DslInternals.Select.Internal uses AntDesign.DslInternals, so a change to AntDesign.DslInternals can break AntDesign.DslInternals.Select.Internal, while a change to AntDesign.DslInternals.Select.Internal can't break AntDesign.DslInternals.
- Position
- Below the diagonal: AntDesign.DslInternals.Select.Internal uses a module listed above it, which is the healthy direction.
38→4 Radzen.Blazor.DslInternals.Blazor.Rendering uses Fun.Blazor✕
- Connections
- 85 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor.Rendering uses a type in Fun.Blazor. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Radzen.Blazor.DslInternals.Blazor.Rendering.AgendaSlotEventsBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.AgendaSlotEventsBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.AgendaViewBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.AppointmentBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.AppointmentBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.CategoryAxisTickBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.CategoryAxisTitleBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.CategoryAxisTitleBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.ChartSharedTooltipBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.ChartSharedTooltipBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.ChartSharedTooltipItemBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.ChartSharedTooltipItemBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.ChartSharedTooltipItemBuilder`1→Fun.Blazor.NodeRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.ChartTooltipBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.ChartTooltipBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.DaySlotEventsBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.DaySlotEventsBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.DayViewBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.DialogContainerBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.DialogContainerBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.DraggableBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.DropableViewBaseBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.DropableViewBaseBuilder`1→Fun.Blazor.ComponentWithDomAndChildAttrBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.EditorButtonBuilder`1→Fun.Blazor.AttrRenderFragmentRadzen.Blazor.DslInternals.Blazor.Rendering.EditorButtonBuilder`1→Fun.Blazor.ComponentWithDomAttrBuilder`1
- Direction
- Radzen.Blazor.DslInternals.Blazor.Rendering uses Fun.Blazor, so a change to Fun.Blazor can break Radzen.Blazor.DslInternals.Blazor.Rendering, while a change to Radzen.Blazor.DslInternals.Blazor.Rendering can't break Fun.Blazor.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor.Rendering uses a module listed above it, which is the healthy direction.
38→19 Radzen.Blazor.DslInternals.Blazor.Rendering uses Radzen.Blazor.DslInternals✕
- Connections
- 2 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor.Rendering uses a type in Radzen.Blazor.DslInternals.
- The types involved
Radzen.Blazor.DslInternals.Blazor.Rendering.DraggableBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.EditorDropDownBuilder`1→Radzen.Blazor.DslInternals.RadzenComponentBuilder`1
- Direction
- Radzen.Blazor.DslInternals.Blazor.Rendering uses Radzen.Blazor.DslInternals, so a change to Radzen.Blazor.DslInternals can break Radzen.Blazor.DslInternals.Blazor.Rendering, while a change to Radzen.Blazor.DslInternals.Blazor.Rendering can't break Radzen.Blazor.DslInternals.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor.Rendering uses a module listed above it, which is the healthy direction.
38→33 Radzen.Blazor.DslInternals.Blazor.Rendering uses Radzen.Blazor.DslInternals.Blazor✕
- Connections
- 4 pairs of types, where a type in Radzen.Blazor.DslInternals.Blazor.Rendering uses a type in Radzen.Blazor.DslInternals.Blazor.
- The types involved
Radzen.Blazor.DslInternals.Blazor.Rendering.CategoryAxisBuilder`1→Radzen.Blazor.DslInternals.Blazor.RadzenChartComponentBaseBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.ClipPathBuilder`1→Radzen.Blazor.DslInternals.Blazor.RadzenChartComponentBaseBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.ValueAxisBuilder`1→Radzen.Blazor.DslInternals.Blazor.RadzenChartComponentBaseBuilder`1Radzen.Blazor.DslInternals.Blazor.Rendering.ValueAxisTitleBuilder`1→Radzen.Blazor.DslInternals.Blazor.RadzenChartComponentBaseBuilder`1
- Direction
- Radzen.Blazor.DslInternals.Blazor.Rendering uses Radzen.Blazor.DslInternals.Blazor, so a change to Radzen.Blazor.DslInternals.Blazor can break Radzen.Blazor.DslInternals.Blazor.Rendering, while a change to Radzen.Blazor.DslInternals.Blazor.Rendering can't break Radzen.Blazor.DslInternals.Blazor.
- Position
- Below the diagonal: Radzen.Blazor.DslInternals.Blazor.Rendering uses a module listed above it, which is the healthy direction.
39→36 AntDesign.Core.Component.ResizeObserver.DslCE uses AntDesign.DslInternals.Core.Component.ResizeObserver✕
- Connections
- 1 pair of types, where a type in AntDesign.Core.Component.ResizeObserver.DslCE uses a type in AntDesign.DslInternals.Core.Component.ResizeObserver.
- The types involved
AntDesign.Core.Component.ResizeObserver.DslCE.ResizeObserver'→AntDesign.DslInternals.Core.Component.ResizeObserver.ResizeObserverBuilder`1
- Direction
- AntDesign.Core.Component.ResizeObserver.DslCE uses AntDesign.DslInternals.Core.Component.ResizeObserver, so a change to AntDesign.DslInternals.Core.Component.ResizeObserver can break AntDesign.Core.Component.ResizeObserver.DslCE, while a change to AntDesign.Core.Component.ResizeObserver.DslCE can't break AntDesign.DslInternals.Core.Component.ResizeObserver.
- Position
- Below the diagonal: AntDesign.Core.Component.ResizeObserver.DslCE uses a module listed above it, which is the healthy direction.
40→37 AntDesign.Select.Internal.DslCE uses AntDesign.DslInternals.Select.Internal✕
- Connections
- 3 pairs of types, where a type in AntDesign.Select.Internal.DslCE uses a type in AntDesign.DslInternals.Select.Internal.
- The types involved
AntDesign.Select.Internal.DslCE.SelectContent'`2→AntDesign.DslInternals.Select.Internal.SelectContentBuilder`3AntDesign.Select.Internal.DslCE.SelectOptionGroup'`2→AntDesign.DslInternals.Select.Internal.SelectOptionGroupBuilder`3AntDesign.Select.Internal.DslCE.SelectSuffixIcon'`2→AntDesign.DslInternals.Select.Internal.SelectSuffixIconBuilder`3
- Direction
- AntDesign.Select.Internal.DslCE uses AntDesign.DslInternals.Select.Internal, so a change to AntDesign.DslInternals.Select.Internal can break AntDesign.Select.Internal.DslCE, while a change to AntDesign.Select.Internal.DslCE can't break AntDesign.DslInternals.Select.Internal.
- Position
- Below the diagonal: AntDesign.Select.Internal.DslCE 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 |
|---|---|---|
| A05:2025 — Injection | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | High / Critical |
Roadmap
Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose; Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. | +7.8 pts | Medium | Access Controls |
| Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose. | +7.4 pts | Medium | Web-Security Posture |
| Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. | +2.4 pts | Low | Dependency Vulnerabilities |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +4.7 pts | Medium | Text alternatives |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +4.3 pts | Medium | Page structure |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.8 pts | Low | Dependency Vulnerabilities |
| 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. | +2.5 pts | Medium | Visual & motion safety |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 5.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| Fun.Blazor/DslComponentBuilder.fs | 6.3 | Mixed | God Classes: TooManyMethods: ComponentWithDomAndChildAttrBuilder`1 |
| Fun.Blazor.HotReload/Interpreter.fs | 7.0 | Mixed | Cyclomatic Complexity: EvalContext.EmitShellTypes (cyclomatic 83) |
| Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs | 7.0 | Mixed | God Classes: FileTooLong: Fun.Blazor.Bindings/Radzen.Blazor.fs |
| Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs | 7.0 | Mixed | God Classes: FileTooLong: Fun.Blazor.Bindings/AntDesign.fs |
| Bindings/Fun.Blazor.MudBlazor/Fun.Blazor.Bindings/MudBlazor.fs | 7.0 | Mixed | God Classes: FileTooLong: Fun.Blazor.Bindings/MudBlazor.fs |
| Fun.Blazor/DslElementBuilder.fs | 7.0 | Mixed | God Classes: TooManyMethods: EltWithChildBuilder |
| Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs | 7.1 | Mixed | God Classes: FileTooLong: Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs |
| Fun.Blazor.HtmlTemplate/Internals.fs | 7.2 | Mixed | Cyclomatic Complexity: Internals.buildAttrs (cyclomatic 21) |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| Fun.Blazor.Generator/CEGenerator.fs | 7.4 | Mixed | Cyclomatic Complexity: CEGenerator.getMetaInfo (cyclomatic 34) |
| Fun.Blazor.Cli/Watch/Processor.fs | 7.8 | Mixed | Cyclomatic Complexity: Processor.process' (cyclomatic 32) |
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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 45 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, 166 of 210 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 or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 |
| Canine Code Analyzer 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 |
Run transparency — what happened this run
- D4 Code Duplication — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Code Duplication couldn't be assessed within its 6-minute budget on a solution this large — not included in this run.
- D8 Code Coverage — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 1020 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 4 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'REDACTED' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (42,902 lines, 100% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Fun.Blazor.Docs.Server/appsettings.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- AC1 Text alternatives — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — and the accessibility cards on this run were measured over the 13 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 13 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — and the accessibility cards on this run were measured over the 13 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 13 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — and the accessibility cards on this run were measured over the 13 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 13 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC4 Keyboard semantics — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — and the accessibility cards on this run were measured over the 13 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 13 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC5 ARIA correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — and the accessibility cards on this run were measured over the 13 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 13 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — and the accessibility cards on this run were measured over the 13 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; 13 of the file(s) above import an HTML builder DSL whose element calls it did not project — a builder it has no reader for, or calls in a shape its reader does not know — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 13 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- 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.
- ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EvalContext.EmitShellTypes at 83.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with EvalContext.EmitShellTypes (cyclomatic 83), EvalContext.EvalCall (cyclomatic 69), EvalContext.EvalExpr (cyclomatic 68). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cyclomatic Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
21 method(s) exceeded the cognitive complexity threshold of 15; the worst was EvalContext.EmitShellTypes at 219.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with EvalContext.EmitShellTypes (cognitive 219). — Refactoring it lifts Cognitive Complexity from 5.5 to about 6.9/10.
D3 · God Classes
81 god class(es) detected.
What to do
- Resolve the 73 TooManyMethods finding(s) in God Classes — start with Radzen.Blazor.fs (21), MudBlazor.fs (21), AntDesign.fs (21). — One of this dimension's main actionable groups (73 warning-level).
- Resolve the 6 FileTooLong finding(s) in God Classes — start with Radzen.Blazor.fs, AntDesign.fs, MudBlazor.fs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 TooManyFunctions finding(s) in God Classes — start with DslHtmxBuilder.fs, DslDomAriaAttr.fs. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
2 of 21 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with DslElementBuilder.fs, DslAdaptiview.fs. — One of this dimension's main actionable groups (2 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 · Dependency Hygiene
38 outdated, 0 vulnerable, 2 deprecated packages.
What to do
- Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED, Fun.Blazor.CustomElements.fsproj, Fun.Blazor.Docs.Wasm.fsproj. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 271 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 38 direct `PackageReference`(s), and 212 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 17 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 48 document(s) read across 2 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 — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
85 % of calls cross a namespace and 3 % go through an interface, but 100 % 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)
14 finding(s): 0 critical, 14 high, 0 medium, 0 low. 13 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
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 13 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 (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 1 critical, 4 high, 1 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 64 of the 114 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: DslElementBuilder.fs↔DslFragmentBuilder.fs 60%; DslComponentBuilder.fs↔DslElementBuilder.fs 50%; FunBlazorComponentWithInlineCE.fs↔DslCore.fs 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with FunBlazorComponentWithInlineCE.fs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with DslComponentBuilder.fs. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 26 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.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — Fun.Blazor.Docs.Wasm/wwwroot/index.html:22
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — Fun.Blazor.Docs.Wasm/wwwroot/index.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — Fun.Blazor.Docs.Wasm/wwwroot/index.html:2
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — Fun.Blazor.Docs.Wasm/wwwroot/index.html:6
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `#app img` moves (`animation: rotation 3s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Fun.Blazor.Docs.Wasm/wwwroot/index.html:39
- `.markdown-body .pl-mi2` sets color: #c9d1d9 on background-color: #1158c7 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Fun.Blazor.Docs.Wasm/wwwroot/css/github-markdown-dark.css:452
- `:not(pre) > code[class*="language-"]` sets color: #db4c69 on background-color: #f9f2f4 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Fun.Blazor.Docs.Wasm/wwwroot/css/prism-vsc-dark-plus.css:44
- `.markdown-body .anchor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — Fun.Blazor.Docs.Wasm/wwwroot/css/github-markdown-dark.css:529, Fun.Blazor.Docs.Wasm/wwwroot/css/github-markdown-light.css:529
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.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX8 · Test isolation
C2 · Access Controls
- No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
What to do
- Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
ED5 · Idempotency
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
- Docs/16 Routing/README.md links to `./routing/#functional-style`, but `Docs/16 Routing/routing` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/16 Routing/README.md:3
- Docs/40 Advanced/82 Custom Elements/README.md names .NET 7, but the projects target .NET 6, 8, 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Docs/40 Advanced/82 Custom Elements/README.md:7
What to do
- Reconcile the README with reality: Docs/16 Routing/README.md links to `./routing/#functional-style`, but `Docs/16 Routing/routing` does not exist; Docs/40 Advanced/82 Custom Elements/README.md names .NET 7, but the projects target .NET 6, 8, 9, 10.
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- Only 2/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `Fun.Blazor.Cli`, `Fun.Blazor.Docs.Server`, `Fun.Blazor.Docs.Wasm`, `Fun.Blazor.Server`, `Fun.Htmx`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
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 5 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:4
- `REDACTED` 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`. — REDACTED:20
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.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `ExecuteAsync` is async and calls .Wait() — a blocking call inside async code stalls the thread-pool thread the workflow runs on, and every continuation queued behind it for as long as it runs. (×2) — Fun.Blazor.Cli/Watch/WatcherServer.fs:42, Fun.Blazor.Cli/Watch/WatcherServer.fs:92
What to do
- F#: inside async { } or task { }, bind with let! / do! (Async.AwaitTask for a Task) instead of Async.RunSynchronously, .Wait() or .GetAwaiter().GetResult(), and use do! Async.Sleep or Task.Delay instead of Thread.Sleep; Async.RunSynchronously belongs at the program's entry point, outside every workflow.
S1 · Web-Security Posture
- `https://unpkg.com/htmx.org@2.0.3` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 6 such include(s) across the repository's markup. — Fun.Blazor.Docs.Server/Index.fs:61
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
- No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
- No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
- Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
- Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
X5 · Nullable reference types
- 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
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 |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 56% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 30% | Weak — gated by C2, S1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 36% | Weak — gated by AC1, AC3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). 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.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC4 Keyboard semantics — AC4 could not be measured here. This repository renders user interface from a template language — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — which this analyzer's markup model does not read (it reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs), so no interactive element from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no interactive element.
- AC5 ARIA correctness — AC5 could not be measured here. This repository renders user interface from a template language — 13 Fun.Blazor (F#) template file(s) carrying 50 markup element(s) (e.g. Fun.Blazor.Tests/Performances.fs, Fun.Blazor.Tests/Rendering/StyleTests.fs, Fun.Blazor.HtmlTemplate/SSRTemplate.fs) — which this analyzer's markup model does not read (it reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs), so no ARIA usage from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no ARIA usage.
- AX1 Captive dependencies — no DI registrations detected
- AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — no public interfaces
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~2290 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 — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository's one project, `CSharpComponents` (17 LoC, 2521 public types across 239 namespaces), is a test, sample, benchmark or tooling project, not a unit of the product. Not scored.
- 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.
- D4 Code Duplication — Code Duplication not included (time budget)
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (65 value object(s))
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 event handler(s))
- 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 — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — X23 reached only 0% of this repository's production lines — fsharp (42,902 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative Fun.Blazor.Docs.Wasm/wwwroot/index.html:22
- <html> without a lang Fun.Blazor.Docs.Wasm/wwwroot/index.html:2
- Viewport restricts zoom Fun.Blazor.Docs.Wasm/wwwroot/index.html:6
- REDACTED
- REDACTED
- Boundary-crossing change coupling: FunBlazorComponentWithInlineCE.fs ↔ DslCore.fs Benchmark/Benchmark/BasicBenchmark/FunBlazorComponentWithInlineCE.fs:1
Serious — 137 finding(s)
- TooManyMethods: RadzenDataGridBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:2759
- TooManyMethods: MudDataGridBuilder`2 Bindings/Fun.Blazor.MudBlazor/Fun.Blazor.Bindings/MudBlazor.fs:1568
- TooManyMethods: RadzenGanttBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:4832
- TooManyMethods: TreeBuilder`2 Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs:2811
- TooManyMethods: MudTableBaseBuilder`1 Bindings/Fun.Blazor.MudBlazor/Fun.Blazor.Bindings/MudBlazor.fs:152
- TooManyMethods: RadzenDatePickerBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:4378
- TooManyMethods: RadzenDataGridColumnBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:10384
- TooManyMethods: RadzenDropDownDataGridBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:1574
- TooManyMethods: RadzenAIChatBuilder`1 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:3566
- TooManyMethods: TableBuilder`2 Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs:2606
- TooManyMethods: RadzenPickListBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:5852
- TooManyMethods: RadzenPivotDataGridBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:3279
- TooManyMethods: MudAutocompleteBuilder`2 Bindings/Fun.Blazor.MudBlazor/Fun.Blazor.Bindings/MudBlazor.fs:529
- TooManyMethods: FluentDataGridBuilder`2 Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs:880
- TooManyMethods: ModalBuilder`1 Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs:2086
- TooManyMethods: ColumnBuilder`2 Bindings/Fun.Blazor.MudBlazor/Fun.Blazor.Bindings/MudBlazor.fs:1395
- TooManyMethods: SelectBaseBuilder`3 Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs:1357
- TooManyMethods: PageHeaderBuilder`1 Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs:2184
- TooManyMethods: RadzenChatBuilder`1 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:4050
- TooManyMethods: DiffEditorBuilder`1 Bindings/Fun.Blazor.BlazorMonaco/Fun.Blazor.Bindings/BlazorMonaco.fs:79
- TooManyMethods: InputBuilder`2 Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs:1230
- TooManyMethods: RadzenSpreadsheetBuilder`1 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:6714
- TooManyMethods: DatePickerBaseBuilder`2 Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs:1108
- TooManyMethods: RadzenTimeSpanPickerBuilder`2 Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs:7361
- TooManyMethods: MudPickerBuilder`2 Bindings/Fun.Blazor.MudBlazor/Fun.Blazor.Bindings/MudBlazor.fs:837
- FileTooLong: Fun.Blazor.Bindings/Radzen.Blazor.fs Bindings/Fun.Blazor.Radzen/Fun.Blazor.Bindings/Radzen.Blazor.fs
- FileTooLong: Fun.Blazor.Bindings/AntDesign.fs Bindings/Fun.Blazor.AntDesign/Fun.Blazor.Bindings/AntDesign.fs
- FileTooLong: Fun.Blazor.Bindings/MudBlazor.fs Bindings/Fun.Blazor.MudBlazor/Fun.Blazor.Bindings/MudBlazor.fs
- FileTooLong: Fun.Blazor.HotReload/Interpreter.fs Fun.Blazor.HotReload/Interpreter.fs
- FileTooLong: Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs Bindings/Fun.Blazor.Microsoft.FluentUI/Fun.Blazor.Bindings/Microsoft.FluentUI.AspNetCore.Components.fs
- FileTooLong: Fun.Blazor/DslDomEventAttr.fs Fun.Blazor/DslDomEventAttr.fs
- Focus outline removed in CSS without a :focus replacement Fun.Blazor.Docs.Wasm/wwwroot/css/github-markdown-dark.css:529
- Focus outline removed in CSS without a :focus replacement Fun.Blazor.Docs.Wasm/wwwroot/css/github-markdown-light.css:529
- Deprecated: Microsoft.AspNetCore.WebUtilities REDACTED:54
- Deprecated: Dotnet.ProjInfo REDACTED:36
- TooManyFunctions: DslHtmxBuilder Fun.Htmx/DslHtmxBuilder.fs:2
- TooManyFunctions: aria Fun.Blazor/DslDomAriaAttr.fs:7
- Low cohesion: EltBuilder (LCOM4 8) Fun.Blazor/DslElementBuilder.fs:8
- Low cohesion: AdaptiviewBuilder (LCOM4 5) Fun.Blazor/DslAdaptiview.fs:15
- Sync-over-async blocking Fun.Blazor.Cli/Watch/WatcherServer.fs:42
- Sync-over-async blocking Fun.Blazor.Cli/Watch/WatcherServer.fs:92
- Page without a main landmark Fun.Blazor.Docs.Wasm/wwwroot/index.html:2
- Animation without a prefers-reduced-motion guard Fun.Blazor.Docs.Wasm/wwwroot/index.html:39
- Low contrast colour pair in CSS (4.2:1) Fun.Blazor.Docs.Wasm/wwwroot/css/github-markdown-dark.css:452
- Low contrast colour pair in CSS (3.6:1) Fun.Blazor.Docs.Wasm/wwwroot/css/prism-vsc-dark-plus.css:44
- No authorization
- EvalContext.EmitShellTypes (cyclomatic 83) Fun.Blazor.HotReload/Interpreter.fs:1039
- EvalContext.EvalCall (cyclomatic 69) Fun.Blazor.HotReload/Interpreter.fs:1988
- EvalContext.EvalExpr (cyclomatic 68) Fun.Blazor.HotReload/Interpreter.fs:1694
- CEGenerator.getMetaInfo (cyclomatic 34) Fun.Blazor.Generator/CEGenerator.fs:20
- Processor.process' (cyclomatic 32) Fun.Blazor.Cli/Watch/Processor.fs:95
- LiveCheckEvaluation.EvaluateDecls (cyclomatic 31) Fun.Blazor.Cli/Watch/LiveCheckEvaluation.fs:315
- FormatExpressions.validateFormat (cyclomatic 25) Fun.Blazor/Router.Giraffe.FormatExpressions.fs:184
- ProjectCracker.getProjectOptionsFromProjectFile (cyclomatic 23) Fun.Blazor.Cli/Watch/ProjectCracker.fs:182
- Internals.buildAttrs (cyclomatic 21) Fun.Blazor.HtmlTemplate/Internals.fs:93
- EvalContext.TryEvalDecls (cyclomatic 20) Fun.Blazor.HotReload/Interpreter.fs:1631
- FunBlazorServerExtensions.MakeCreateAttrFn (cyclomatic 20) Fun.Blazor.Server/DIExtensions.fs:179
- Utils.getTypeName (cyclomatic 18) Fun.Blazor.Generator/Utils.fs:111
- Utils.reload (cyclomatic 18) Fun.Blazor.HotReload/Utils.fs:37
- HxTrigger.AddTrigger (cyclomatic 17) Fun.Htmx/Core.fs:529
- MetaInfo.create (cyclomatic 16) Fun.Blazor.Generator/MetaInfo.fs:23
- EvalContext.EmitShellTypes (cognitive 219) Fun.Blazor.HotReload/Interpreter.fs:1039
- CEGenerator.getMetaInfo (cognitive 52) Fun.Blazor.Generator/CEGenerator.fs:20
- Processor.process' (cognitive 48) Fun.Blazor.Cli/Watch/Processor.fs:95
- LiveCheckEvaluation.EvaluateDecls (cognitive 47) Fun.Blazor.Cli/Watch/LiveCheckEvaluation.fs:315
- EvalContext.TryEvalDecls (cognitive 46) Fun.Blazor.HotReload/Interpreter.fs:1631
- Utils.reload (cognitive 46) Fun.Blazor.HotReload/Utils.fs:37
- Internals.buildAttrs (cognitive 45) Fun.Blazor.HtmlTemplate/Internals.fs:93
- EvalContext.EvalExpr (cognitive 40) Fun.Blazor.HotReload/Interpreter.fs:1694
- FormatExpressions.validateFormat (cognitive 39) Fun.Blazor/Router.Giraffe.FormatExpressions.fs:184
- DIComponent`1.HandleNotFoundType (cognitive 37) Fun.Blazor/DIComponent.fs:165
- Utils.getTypeName (cognitive 34) Fun.Blazor.Generator/Utils.fs:111
- FunBlazorServerExtensions.MakeCreateAttrFn (cognitive 31) Fun.Blazor.Server/DIExtensions.fs:179
- EvalContext.EvalCall (cognitive 30) Fun.Blazor.HotReload/Interpreter.fs:1988
- Internals.parseNodes (cognitive 27) Fun.Blazor.HtmlTemplate/Internals.fs:238
- SSRTemplate.html (cognitive 26) Fun.Blazor.HtmlTemplate/SSRTemplate.fs:18
- ProjectCracker.getProjectOptionsFromProjectFile (cognitive 20) Fun.Blazor.Cli/Watch/ProjectCracker.fs:182
- Generate.findPackageMetas (cognitive 18) Fun.Blazor.Cli/CodeGen/Generate.fs:45
- CEGenerator.generateCode (cognitive 18) Fun.Blazor.Generator/CEGenerator.fs:213
- MetaInfo.create (cognitive 18) Fun.Blazor.Generator/MetaInfo.fs:23
- HxTrigger.AddTrigger (cognitive 17) Fun.Htmx/Core.fs:529
- Internals.buildNodes (cognitive 16) Fun.Blazor.HtmlTemplate/Internals.fs:33
- REDACTED
- Change coupling clique: DslComponentBuilder.fs, DslElementBuilder.fs, DslFragmentBuilder.fs Fun.Blazor/DslComponentBuilder.fs
- REDACTED
- REDACTED
- REDACTED
- Third-party script without Subresource Integrity Fun.Blazor.Docs.Server/Index.fs:61
- NuGet dependencies are not locked
Minor — 15 finding(s)
- Outdated: Microsoft.Extensions.ObjectPool REDACTED:50
- Outdated: Microsoft.AspNetCore.Components.CustomElements Fun.Blazor.CustomElements/Fun.Blazor.CustomElements.fsproj:24
- Outdated: BlazorWasmPreRendering.Build Fun.Blazor.Docs.Wasm/Fun.Blazor.Docs.Wasm.fsproj:50
- README/code drift Docs/16 Routing/README.md:3
- README/code drift Docs/40 Advanced/82 Custom Elements/README.md:7
- No ADRs found REDACTED:4
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:4
- No dependency-update automation REDACTED:20
- No security response headers detected
- No app-layer HTTPS enforcement detected
- No inbound model validation detected
- Nullable reference types not enabled everywhere
Minor — 35 finding(s)
- Outdated: FSharp.Core
- Outdated: FSharp.Data.Adaptive
- Outdated: Microsoft.AspNetCore.Components.Web
- Outdated: Microsoft.AspNetCore.WebUtilities
- Outdated: CliWrap
- Outdated: FSharp.Compiler.Service
- Outdated: Microsoft.Build.Utilities.Core
- Outdated: Spectre.Console
- Outdated: Spectre.Console.Cli
- Outdated: Elmish
- Outdated: Microsoft.AspNetCore.SignalR.Client
- Outdated: FSharp.Data
- Outdated: FSharp.Control.Reactive
- Outdated: FSharp.SystemTextJson
- Outdated: Microsoft.AspNetCore.Components.WebAssembly
- Outdated: bunit
- Outdated: FsUnit.xUnit
- Outdated: Microsoft.AspNetCore.TestHost
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: Microsoft.Testing.Extensions.CodeCoverage
- Outdated: Moq
- Outdated: xunit.runner.visualstudio
- Outdated: xunit.v3
- Outdated: Majorsoft.Blazor.WebAssembly.Logging.Console
- Outdated: Microsoft.AspNetCore.Components.WebAssembly.DevServer
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7c80e67d21b7498e89fb9d8dda81649b/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7c80e67d21b7498e89fb9d8dda81649b/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/canine-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 . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Fun.Blazor.sln package --vulnerable --include-transitive --format json | 6 | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-c5419ed7779e4b6fa19c292c448fe0e2 | 0 | artifacts/raw/osv-scanner.json |