Executive summary
sydsutton/FS.FluentUI falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 58 out of 100 and is rated Adequate, and three of its five critical findings are security problems in the build pipeline.
Production Readiness, at 41, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the three deprecated dependencies, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, worth about 9 points. Raising Production Readiness to 70 would lift the score to about 69.
Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version and making the hidden dependencies explicit would close both risks.
The product code is 39,504 lines, about €41,000 to rebuild.
If Production Readiness rose from 41 to 70, the lowest score rated Strong, the score would rise from 58 to about 69.
New since the last survey: 4 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- CI/CD gates · No CI pipeline
Rebuild cost: about €41,000 · Estimate
| Cost to rebuild | €14,000 to €68,000, for 227 to 719 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. 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: 39,504 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: which parts of the code depend on which
| uses → | 1 FluentUI | 2 FluentUI.Charts | 3 FluentUI.V8toV9 | 4 FullCalendar | 5 FluentUI.Charts.areaChartModule | 6 FluentUI.Charts.areaPolarSeriesModule | 7 FluentUI.Charts.barSeriesModule | 8 FluentUI.Charts.chartAnnotationConnectorModule | 9 FluentUI.Charts.chartAnnotationCoordinateModule | 10 FluentUI.Charts.chartAnnotationLayoutModule | 11 FluentUI.Charts.chartPopoverPropModule | 12 FluentUI.Charts.dateTimeFormatOptionsModule | 13 FluentUI.Charts.funnelChartModule | 14 FluentUI.Charts.gaugeChartModule | 15 FluentUI.Charts.groupedVerticalBarChartModule | 16 FluentUI.Charts.heatMapChartModule | 17 FluentUI.Charts.horizontalBarChartModule | 18 FluentUI.Charts.lineChartLineOptionsModule | 19 FluentUI.Charts.lineChartPointsModule | 20 FluentUI.Charts.linePolarSeriesModule | 21 FluentUI.Charts.lineSeriesModule | 22 FluentUI.Charts.numberFormatOptionsModule | 23 FluentUI.Charts.polarAxisPropModule | 24 FluentUI.Charts.polarChartModule | 25 FluentUI.Charts.scatterPolarSeriesModule | 26 FluentUI.Charts.verticalBarChartModule | 27 FluentUI.Charts.verticalStackedBarChartModule | 28 FluentUI.CheckStateModule | 29 FluentUI.DateFormat | 30 FluentUI.DatePickerErrorStringsModule | 31 FluentUI.DatePickerValidationResultDataModule | 32 FluentUI.FieldControlPropsModule | 33 FluentUI.FuiModule | 34 FluentUI.ImageSwatch | 35 FluentUI.TempSeq | 36 FluentUI.TimeSelectionDataModule | 37 FluentUI.V8toV9.stackItemModule | 38 FluentUI.V8toV9.stackModule | 39 FluentUI.accordionHeaderModule | 40 FluentUI.accordionModule |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 FluentUI | ||||||||||||||||||||||||||||||||||||||||
| 2 FluentUI.Charts | ||||||||||||||||||||||||||||||||||||||||
| 3 FluentUI.V8toV9 | ||||||||||||||||||||||||||||||||||||||||
| 4 FullCalendar | ||||||||||||||||||||||||||||||||||||||||
| 5 FluentUI.Charts.areaChartModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 FluentUI.Charts.areaPolarSeriesModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 FluentUI.Charts.barSeriesModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 FluentUI.Charts.chartAnnotationConnectorModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 FluentUI.Charts.chartAnnotationCoordinateModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 10 FluentUI.Charts.chartAnnotationLayoutModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 FluentUI.Charts.chartPopoverPropModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 FluentUI.Charts.dateTimeFormatOptionsModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 13 FluentUI.Charts.funnelChartModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 FluentUI.Charts.gaugeChartModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 FluentUI.Charts.groupedVerticalBarChartModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 FluentUI.Charts.heatMapChartModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 FluentUI.Charts.horizontalBarChartModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 FluentUI.Charts.lineChartLineOptionsModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 FluentUI.Charts.lineChartPointsModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 FluentUI.Charts.linePolarSeriesModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 FluentUI.Charts.lineSeriesModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 FluentUI.Charts.numberFormatOptionsModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 FluentUI.Charts.polarAxisPropModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 FluentUI.Charts.polarChartModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 FluentUI.Charts.scatterPolarSeriesModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 FluentUI.Charts.verticalBarChartModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 FluentUI.Charts.verticalStackedBarChartModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 28 FluentUI.CheckStateModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 FluentUI.DateFormat | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 FluentUI.DatePickerErrorStringsModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 FluentUI.DatePickerValidationResultDataModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 FluentUI.FieldControlPropsModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 FluentUI.FuiModule | 11 | |||||||||||||||||||||||||||||||||||||||
| 34 FluentUI.ImageSwatch | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 FluentUI.TempSeq | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 FluentUI.TimeSelectionDataModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 FluentUI.V8toV9.stackItemModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 38 FluentUI.V8toV9.stackModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 39 FluentUI.accordionHeaderModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 40 FluentUI.accordionModule | 2 |
5→2 FluentUI.Charts.areaChartModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.areaChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.areaChartModule.mode→FS.FluentUI.Charts.IAreaChartProp
- Direction
- FluentUI.Charts.areaChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.areaChartModule, while a change to FluentUI.Charts.areaChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.areaChartModule uses a module listed above it, which is the healthy direction.
6→2 FluentUI.Charts.areaPolarSeriesModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.areaPolarSeriesModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.areaPolarSeriesModule.type'→FS.FluentUI.Charts.IAreaPolarSeriesProp
- Direction
- FluentUI.Charts.areaPolarSeriesModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.areaPolarSeriesModule, while a change to FluentUI.Charts.areaPolarSeriesModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.areaPolarSeriesModule uses a module listed above it, which is the healthy direction.
7→2 FluentUI.Charts.barSeriesModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.barSeriesModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.barSeriesModule.type'→FS.FluentUI.Charts.IBarSeriesProp
- Direction
- FluentUI.Charts.barSeriesModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.barSeriesModule, while a change to FluentUI.Charts.barSeriesModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.barSeriesModule uses a module listed above it, which is the healthy direction.
8→2 FluentUI.Charts.chartAnnotationConnectorModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.chartAnnotationConnectorModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.chartAnnotationConnectorModule.arrow→FS.FluentUI.Charts.IChartAnnotationConnectorProp
- Direction
- FluentUI.Charts.chartAnnotationConnectorModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.chartAnnotationConnectorModule, while a change to FluentUI.Charts.chartAnnotationConnectorModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.chartAnnotationConnectorModule uses a module listed above it, which is the healthy direction.
9→2 FluentUI.Charts.chartAnnotationCoordinateModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.chartAnnotationCoordinateModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.chartAnnotationCoordinateModule.type'→FS.FluentUI.Charts.IChartAnnotationCoordinatePropFS.FluentUI.Charts.chartAnnotationCoordinateModule.yAxis→FS.FluentUI.Charts.IChartAnnotationCoordinateProp
- Direction
- FluentUI.Charts.chartAnnotationCoordinateModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.chartAnnotationCoordinateModule, while a change to FluentUI.Charts.chartAnnotationCoordinateModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.chartAnnotationCoordinateModule uses a module listed above it, which is the healthy direction.
10→2 FluentUI.Charts.chartAnnotationLayoutModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.chartAnnotationLayoutModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.chartAnnotationLayoutModule.align→FS.FluentUI.Charts.IChartAnnotationLayoutPropFS.FluentUI.Charts.chartAnnotationLayoutModule.verticalAlign→FS.FluentUI.Charts.IChartAnnotationLayoutProp
- Direction
- FluentUI.Charts.chartAnnotationLayoutModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.chartAnnotationLayoutModule, while a change to FluentUI.Charts.chartAnnotationLayoutModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.chartAnnotationLayoutModule uses a module listed above it, which is the healthy direction.
11→2 FluentUI.Charts.chartPopoverPropModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.chartPopoverPropModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.chartPopoverPropModule.customCallout→FS.FluentUI.Charts.IChartPopoverPropFS.FluentUI.Charts.chartPopoverPropModule.xAxisCalloutAccessibilityData→FS.FluentUI.Charts.IChartPopoverProp
- Direction
- FluentUI.Charts.chartPopoverPropModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.chartPopoverPropModule, while a change to FluentUI.Charts.chartPopoverPropModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.chartPopoverPropModule uses a module listed above it, which is the healthy direction.
12→2 FluentUI.Charts.dateTimeFormatOptionsModule uses FluentUI.Charts✕
- Connections
- 4 pairs of types, where a type in FluentUI.Charts.dateTimeFormatOptionsModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.dateTimeFormatOptionsModule.dateStyle→FS.FluentUI.Charts.IDateTimeFormatOptionsPropFS.FluentUI.Charts.dateTimeFormatOptionsModule.dayPeriod→FS.FluentUI.Charts.IDateTimeFormatOptionsPropFS.FluentUI.Charts.dateTimeFormatOptionsModule.hourCycle→FS.FluentUI.Charts.IDateTimeFormatOptionsPropFS.FluentUI.Charts.dateTimeFormatOptionsModule.timeStyle→FS.FluentUI.Charts.IDateTimeFormatOptionsProp
- Direction
- FluentUI.Charts.dateTimeFormatOptionsModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.dateTimeFormatOptionsModule, while a change to FluentUI.Charts.dateTimeFormatOptionsModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.dateTimeFormatOptionsModule uses a module listed above it, which is the healthy direction.
13→2 FluentUI.Charts.funnelChartModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.funnelChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.funnelChartModule.orientation→FS.FluentUI.Charts.IFunnelChartProp
- Direction
- FluentUI.Charts.funnelChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.funnelChartModule, while a change to FluentUI.Charts.funnelChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.funnelChartModule uses a module listed above it, which is the healthy direction.
14→2 FluentUI.Charts.gaugeChartModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.gaugeChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.gaugeChartModule.chartValueFormat→FS.FluentUI.Charts.IGaugeChartPropFS.FluentUI.Charts.gaugeChartModule.variant→FS.FluentUI.Charts.IGaugeChartProp
- Direction
- FluentUI.Charts.gaugeChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.gaugeChartModule, while a change to FluentUI.Charts.gaugeChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.gaugeChartModule uses a module listed above it, which is the healthy direction.
15→2 FluentUI.Charts.groupedVerticalBarChartModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.groupedVerticalBarChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.groupedVerticalBarChartModule.barWidth→FS.FluentUI.Charts.IGroupedVerticalBarChartPropFS.FluentUI.Charts.groupedVerticalBarChartModule.mode→FS.FluentUI.Charts.IGroupedVerticalBarChartProp
- Direction
- FluentUI.Charts.groupedVerticalBarChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.groupedVerticalBarChartModule, while a change to FluentUI.Charts.groupedVerticalBarChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.groupedVerticalBarChartModule uses a module listed above it, which is the healthy direction.
16→2 FluentUI.Charts.heatMapChartModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.heatMapChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.heatMapChartModule.sortOrder→FS.FluentUI.Charts.IHeatMapChartProp
- Direction
- FluentUI.Charts.heatMapChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.heatMapChartModule, while a change to FluentUI.Charts.heatMapChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.heatMapChartModule uses a module listed above it, which is the healthy direction.
17→2 FluentUI.Charts.horizontalBarChartModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.horizontalBarChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.horizontalBarChartModule.chartDataMode→FS.FluentUI.Charts.IHorizontalBarChartPropFS.FluentUI.Charts.horizontalBarChartModule.variant→FS.FluentUI.Charts.IHorizontalBarChartProp
- Direction
- FluentUI.Charts.horizontalBarChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.horizontalBarChartModule, while a change to FluentUI.Charts.horizontalBarChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.horizontalBarChartModule uses a module listed above it, which is the healthy direction.
18→2 FluentUI.Charts.lineChartLineOptionsModule uses FluentUI.Charts✕
- Connections
- 3 pairs of types, where a type in FluentUI.Charts.lineChartLineOptionsModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.lineChartLineOptionsModule.curve→FS.FluentUI.Charts.ILineChartLineOptionsPropFS.FluentUI.Charts.lineChartLineOptionsModule.mode→FS.FluentUI.Charts.ILineChartLineOptionsPropFS.FluentUI.Charts.lineChartLineOptionsModule.strokeLinecap→FS.FluentUI.Charts.ILineChartLineOptionsProp
- Direction
- FluentUI.Charts.lineChartLineOptionsModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.lineChartLineOptionsModule, while a change to FluentUI.Charts.lineChartLineOptionsModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.lineChartLineOptionsModule uses a module listed above it, which is the healthy direction.
19→2 FluentUI.Charts.lineChartPointsModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.lineChartPointsModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.lineChartPointsModule.legendShape→FS.FluentUI.Charts.ILineChartPointsProp
- Direction
- FluentUI.Charts.lineChartPointsModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.lineChartPointsModule, while a change to FluentUI.Charts.lineChartPointsModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.lineChartPointsModule uses a module listed above it, which is the healthy direction.
20→2 FluentUI.Charts.linePolarSeriesModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.linePolarSeriesModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.linePolarSeriesModule.type'→FS.FluentUI.Charts.ILinePolarSeriesProp
- Direction
- FluentUI.Charts.linePolarSeriesModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.linePolarSeriesModule, while a change to FluentUI.Charts.linePolarSeriesModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.linePolarSeriesModule uses a module listed above it, which is the healthy direction.
21→2 FluentUI.Charts.lineSeriesModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.lineSeriesModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.lineSeriesModule.type'→FS.FluentUI.Charts.ILineSeriesProp
- Direction
- FluentUI.Charts.lineSeriesModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.lineSeriesModule, while a change to FluentUI.Charts.lineSeriesModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.lineSeriesModule uses a module listed above it, which is the healthy direction.
22→2 FluentUI.Charts.numberFormatOptionsModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.numberFormatOptionsModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.numberFormatOptionsModule.localeMatcher→FS.FluentUI.Charts.INumberFormatOptionsProp
- Direction
- FluentUI.Charts.numberFormatOptionsModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.numberFormatOptionsModule, while a change to FluentUI.Charts.numberFormatOptionsModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.numberFormatOptionsModule uses a module listed above it, which is the healthy direction.
23→2 FluentUI.Charts.polarAxisPropModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.polarAxisPropModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.polarAxisPropModule.unit→FS.FluentUI.Charts.IPolarAxisProp
- Direction
- FluentUI.Charts.polarAxisPropModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.polarAxisPropModule, while a change to FluentUI.Charts.polarAxisPropModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.polarAxisPropModule uses a module listed above it, which is the healthy direction.
24→2 FluentUI.Charts.polarChartModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.polarChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.polarChartModule.direction→FS.FluentUI.Charts.IPolarChartPropFS.FluentUI.Charts.polarChartModule.shape→FS.FluentUI.Charts.IPolarChartProp
- Direction
- FluentUI.Charts.polarChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.polarChartModule, while a change to FluentUI.Charts.polarChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.polarChartModule uses a module listed above it, which is the healthy direction.
25→2 FluentUI.Charts.scatterPolarSeriesModule uses FluentUI.Charts✕
- Connections
- 1 pair of types, where a type in FluentUI.Charts.scatterPolarSeriesModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.scatterPolarSeriesModule.type'→FS.FluentUI.Charts.IScatterPolarSeriesProp
- Direction
- FluentUI.Charts.scatterPolarSeriesModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.scatterPolarSeriesModule, while a change to FluentUI.Charts.scatterPolarSeriesModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.scatterPolarSeriesModule uses a module listed above it, which is the healthy direction.
26→2 FluentUI.Charts.verticalBarChartModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.verticalBarChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.verticalBarChartModule.barWidth→FS.FluentUI.Charts.IVerticalBarChartPropFS.FluentUI.Charts.verticalBarChartModule.mode→FS.FluentUI.Charts.IVerticalBarChartProp
- Direction
- FluentUI.Charts.verticalBarChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.verticalBarChartModule, while a change to FluentUI.Charts.verticalBarChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.verticalBarChartModule uses a module listed above it, which is the healthy direction.
27→2 FluentUI.Charts.verticalStackedBarChartModule uses FluentUI.Charts✕
- Connections
- 2 pairs of types, where a type in FluentUI.Charts.verticalStackedBarChartModule uses a type in FluentUI.Charts.
- The types involved
FS.FluentUI.Charts.verticalStackedBarChartModule.barWidth→FS.FluentUI.Charts.IVerticalStackedBarChartPropFS.FluentUI.Charts.verticalStackedBarChartModule.mode→FS.FluentUI.Charts.IVerticalStackedBarChartProp
- Direction
- FluentUI.Charts.verticalStackedBarChartModule uses FluentUI.Charts, so a change to FluentUI.Charts can break FluentUI.Charts.verticalStackedBarChartModule, while a change to FluentUI.Charts.verticalStackedBarChartModule can't break FluentUI.Charts.
- Position
- Below the diagonal: FluentUI.Charts.verticalStackedBarChartModule uses a module listed above it, which is the healthy direction.
28→1 FluentUI.CheckStateModule uses FluentUI✕
- Connections
- 1 pair of types, where a type in FluentUI.CheckStateModule uses a type in FluentUI.
- The types involved
FS.FluentUI.CheckStateModule.CheckStateModule→FS.FluentUI.CheckState
- Direction
- FluentUI.CheckStateModule uses FluentUI, so a change to FluentUI can break FluentUI.CheckStateModule, while a change to FluentUI.CheckStateModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.CheckStateModule uses a module listed above it, which is the healthy direction.
29→1 FluentUI.DateFormat uses FluentUI✕
- Connections
- 1 pair of types, where a type in FluentUI.DateFormat uses a type in FluentUI.
- The types involved
FS.FluentUI.DateFormat.DateFormat→FS.FluentUI.DateFormatting
- Direction
- FluentUI.DateFormat uses FluentUI, so a change to FluentUI can break FluentUI.DateFormat, while a change to FluentUI.DateFormat can't break FluentUI.
- Position
- Below the diagonal: FluentUI.DateFormat uses a module listed above it, which is the healthy direction.
30→1 FluentUI.DatePickerErrorStringsModule uses FluentUI✕
- Connections
- 1 pair of types, where a type in FluentUI.DatePickerErrorStringsModule uses a type in FluentUI.
- The types involved
FS.FluentUI.DatePickerErrorStringsModule.DatePickerErrorStringsModule→FS.FluentUI.DatePickerErrorType
- Direction
- FluentUI.DatePickerErrorStringsModule uses FluentUI, so a change to FluentUI can break FluentUI.DatePickerErrorStringsModule, while a change to FluentUI.DatePickerErrorStringsModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.DatePickerErrorStringsModule uses a module listed above it, which is the healthy direction.
31→1 FluentUI.DatePickerValidationResultDataModule uses FluentUI✕
- Connections
- 1 pair of types, where a type in FluentUI.DatePickerValidationResultDataModule uses a type in FluentUI.
- The types involved
FS.FluentUI.DatePickerValidationResultDataModule.DatePickerValidationResultDataModule→FS.FluentUI.DatePickerValidationResultData
- Direction
- FluentUI.DatePickerValidationResultDataModule uses FluentUI, so a change to FluentUI can break FluentUI.DatePickerValidationResultDataModule, while a change to FluentUI.DatePickerValidationResultDataModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.DatePickerValidationResultDataModule uses a module listed above it, which is the healthy direction.
32→1 FluentUI.FieldControlPropsModule uses FluentUI✕
- Connections
- 1 pair of types, where a type in FluentUI.FieldControlPropsModule uses a type in FluentUI.
- The types involved
FS.FluentUI.FieldControlPropsModule.FieldControlPropsModule→FS.FluentUI.FieldControlProps
- Direction
- FluentUI.FieldControlPropsModule uses FluentUI, so a change to FluentUI can break FluentUI.FieldControlPropsModule, while a change to FluentUI.FieldControlPropsModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.FieldControlPropsModule uses a module listed above it, which is the healthy direction.
33→1 FluentUI.FuiModule uses FluentUI✕
- Connections
- 11 pairs of types, where a type in FluentUI.FuiModule uses a type in FluentUI.
- The types involved
FS.FluentUI.FuiModule.FuiModule→FS.FluentUI.TinyColorFS.FluentUI.FuiModule.icon→FS.FluentUI.IIconPropFS.FluentUI.FuiModule.text→FS.FluentUI.ITextPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IDataGridBodyPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IDataGridCellPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IDataGridHeaderCellPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IDataGridHeaderPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IDataGridPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IDataGridRowPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IDataGridSelectionCellPropFS.FluentUI.FuiModule.virtualized→FS.FluentUI.IVirtualizedListProp
- Direction
- FluentUI.FuiModule uses FluentUI, so a change to FluentUI can break FluentUI.FuiModule, while a change to FluentUI.FuiModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.FuiModule uses a module listed above it, which is the healthy direction.
34→1 FluentUI.ImageSwatch uses FluentUI✕
- Connections
- 2 pairs of types, where a type in FluentUI.ImageSwatch uses a type in FluentUI.
- The types involved
FS.FluentUI.ImageSwatch.shape→FS.FluentUI.IImageSwatchPropFS.FluentUI.ImageSwatch.size→FS.FluentUI.IImageSwatchProp
- Direction
- FluentUI.ImageSwatch uses FluentUI, so a change to FluentUI can break FluentUI.ImageSwatch, while a change to FluentUI.ImageSwatch can't break FluentUI.
- Position
- Below the diagonal: FluentUI.ImageSwatch uses a module listed above it, which is the healthy direction.
35→1 FluentUI.TempSeq uses FluentUI✕
- Connections
- 2 pairs of types, where a type in FluentUI.TempSeq uses a type in FluentUI.
- The types involved
FS.FluentUI.TempSeq.TempSeq→FS.FluentUI.OnSelectionChangeData`1FS.FluentUI.TempSeq.TempSeq→FS.FluentUI.TempSeq`1
- Direction
- FluentUI.TempSeq uses FluentUI, so a change to FluentUI can break FluentUI.TempSeq, while a change to FluentUI.TempSeq can't break FluentUI.
- Position
- Below the diagonal: FluentUI.TempSeq uses a module listed above it, which is the healthy direction.
36→1 FluentUI.TimeSelectionDataModule uses FluentUI✕
- Connections
- 1 pair of types, where a type in FluentUI.TimeSelectionDataModule uses a type in FluentUI.
- The types involved
FS.FluentUI.TimeSelectionDataModule.TimeSelectionDataModule→FS.FluentUI.TimeSelectionData
- Direction
- FluentUI.TimeSelectionDataModule uses FluentUI, so a change to FluentUI can break FluentUI.TimeSelectionDataModule, while a change to FluentUI.TimeSelectionDataModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.TimeSelectionDataModule uses a module listed above it, which is the healthy direction.
37→3 FluentUI.V8toV9.stackItemModule uses FluentUI.V8toV9✕
- Connections
- 3 pairs of types, where a type in FluentUI.V8toV9.stackItemModule uses a type in FluentUI.V8toV9.
- The types involved
FS.FluentUI.V8toV9.stackItemModule.align→FS.FluentUI.V8toV9.IStackItemPropFS.FluentUI.V8toV9.stackItemModule.grow→FS.FluentUI.V8toV9.IStackItemPropFS.FluentUI.V8toV9.stackItemModule.shrink→FS.FluentUI.V8toV9.IStackItemProp
- Direction
- FluentUI.V8toV9.stackItemModule uses FluentUI.V8toV9, so a change to FluentUI.V8toV9 can break FluentUI.V8toV9.stackItemModule, while a change to FluentUI.V8toV9.stackItemModule can't break FluentUI.V8toV9.
- Position
- Below the diagonal: FluentUI.V8toV9.stackItemModule uses a module listed above it, which is the healthy direction.
38→3 FluentUI.V8toV9.stackModule uses FluentUI.V8toV9✕
- Connections
- 4 pairs of types, where a type in FluentUI.V8toV9.stackModule uses a type in FluentUI.V8toV9.
- The types involved
FS.FluentUI.V8toV9.stackModule.grow→FS.FluentUI.V8toV9.IStackPropFS.FluentUI.V8toV9.stackModule.horizontalAlign→FS.FluentUI.V8toV9.IStackPropFS.FluentUI.V8toV9.stackModule.tokens→FS.FluentUI.V8toV9.IStackTokensPropFS.FluentUI.V8toV9.stackModule.verticalAlign→FS.FluentUI.V8toV9.IStackProp
- Direction
- FluentUI.V8toV9.stackModule uses FluentUI.V8toV9, so a change to FluentUI.V8toV9 can break FluentUI.V8toV9.stackModule, while a change to FluentUI.V8toV9.stackModule can't break FluentUI.V8toV9.
- Position
- Below the diagonal: FluentUI.V8toV9.stackModule uses a module listed above it, which is the healthy direction.
39→1 FluentUI.accordionHeaderModule uses FluentUI✕
- Connections
- 2 pairs of types, where a type in FluentUI.accordionHeaderModule uses a type in FluentUI.
- The types involved
FS.FluentUI.accordionHeaderModule.expandIconPosition→FS.FluentUI.IAccordionHeaderPropFS.FluentUI.accordionHeaderModule.size→FS.FluentUI.IAccordionHeaderProp
- Direction
- FluentUI.accordionHeaderModule uses FluentUI, so a change to FluentUI can break FluentUI.accordionHeaderModule, while a change to FluentUI.accordionHeaderModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.accordionHeaderModule uses a module listed above it, which is the healthy direction.
40→1 FluentUI.accordionModule uses FluentUI✕
- Connections
- 2 pairs of types, where a type in FluentUI.accordionModule uses a type in FluentUI.
- The types involved
FS.FluentUI.accordionModule.as'→FS.FluentUI.IAccordionPropFS.FluentUI.accordionModule.navigation→FS.FluentUI.IAccordionProp
- Direction
- FluentUI.accordionModule uses FluentUI, so a change to FluentUI can break FluentUI.accordionModule, while a change to FluentUI.accordionModule can't break FluentUI.
- Position
- Below the diagonal: FluentUI.accordionModule 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; 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; Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with package-lock.json (3).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with package-lock.json (3). | +5.3 pts | Low | Dependency Hygiene |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.8 pts | Medium | Observability |
| 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. | +7.2 pts | Medium | Architecture documentation |
| Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with FS.FluentUI.Charts.fsproj, TestGrounds.fsproj. | +3.6 pts | Low | Dependency Hygiene |
| Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene. | +1.8 pts | Low | Dependency Hygiene |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/FS.FluentUI/inline-style-expand-shorthand.js | 7.1 | Mixed | Cyclomatic Complexity: inline-style-expand-shorthand.expandProperty (cyclomatic 17) |
| src/FS.FluentUI/Props2.fs | 7.1 | Mixed | God Classes: FileTooLong: FS.FluentUI/Props2.fs |
| src/FS.FluentUI/FluentUI.fs | 7.2 | Mixed | God Classes: TooManyMethods: icon |
| src/FS.FluentUI.Charts/Props.fs | 7.2 | Mixed | God Classes: FileTooLong: FS.FluentUI.Charts/Props.fs |
| src/FS.FullCalendar/Props.fs | 7.4 | Mixed | God Classes: TooManyMethods: calendar |
| src/FS.FluentUI.V8toV9/FelizProps.fs | 7.8 | Mixed | God Classes: TooManyMethods: prop`1 |
| src/FS.FluentUI/FelizProps.fs | 7.8 | Mixed | God Classes: TooManyMethods: prop`1 |
| src/FS.FluentUI/Props.fs | 7.8 | Mixed | God Classes: FileTooLong: FS.FluentUI/Props.fs |
| src/FS.FluentUI.Charts/Utils.fs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: Utils.fs ↔ TestCharts.fs |
| src/FS.FluentUI.TestGrounds/src/TestGrounds.fs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: TestGrounds.fs ↔ Utils.fs |
| src/FS.FluentUI/BundleIcons.fs | 8.5 | Near-clean | God Classes: FileTooLong: FS.FluentUI/BundleIcons.fs |
| src/FS.FluentUI/Domain.fs | 8.5 | Near-clean | God Classes: FileTooLong: FS.FluentUI/Domain.fs |
| src/FS.FullCalendar/Domain.fs | 8.5 | Near-clean | God Classes: FileTooLong: FS.FullCalendar/Domain.fs |
| src/FS.FluentUI.TestGrounds/package-lock.json | 9.1 | Near-clean | Dependency Hygiene: Deprecated: querystring |
| src/FS.FluentUI.Charts/FS.FluentUI.Charts.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: FSharp.Core |
| src/FS.FluentUI.TestGrounds/src/TestGrounds.fsproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: Feliz.UseElmish |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 35 of 35 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 35 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, 41 of 134 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D4 Code Duplication — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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).
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- 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 (6 contributor(s) across 540 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 5 hold 1.8% 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.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 2 of 3 declared ecosystem(s) (npm,nuget) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
- D43 Malicious Dependencies — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies.
- AC1 Text alternatives — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs) — and the accessibility cards on this run were measured over the 0 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; 7 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs) — and the accessibility cards on this run were measured over the 0 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; 7 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs) — and the accessibility cards on this run were measured over the 0 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; 7 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs) — and the accessibility cards on this run were measured over the 0 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; 7 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs) — and the accessibility cards on this run were measured over the 0 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; 7 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs) — and the accessibility cards on this run were measured over the 0 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; 7 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.
- AC7 A11y enforcement — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository renders user interface from a TEMPLATE LANGUAGE or a host-language HTML BUILDER — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs) — and the accessibility cards on this run were measured over the 0 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; 7 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.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M3 Folder & project structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
- P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A 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.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was inline-style-expand-shorthand.expandProperty at 17.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with inline-style-expand-shorthand.expandProperty (cyclomatic 17), expandProperty (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was inline-style-expand-shorthand.expandWithMerge at 21.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with inline-style-expand-shorthand.expandWithMerge (cognitive 21), expandWithMerge (cognitive 21), inline-style-expand-shorthand.parseTextDecoration (cognitive 18). — 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 8 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
25 god class(es) detected.
What to do
- Resolve the 15 TooManyMethods finding(s) in God Classes — start with Props.fs (6), Props2.fs (4), FluentUI.fs (3). — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 10 FileTooLong finding(s) in God Classes — start with Props.fs (3), Domain.fs (2), FelizProps.fs (2). — One of this dimension's main actionable groups (10 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D5 · Coupling
5 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D12 · Dependency Hygiene
5 outdated, 0 vulnerable, 0 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 79 outdated of 174 package(s) across 1 lockfile(s).
What to do
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with package-lock.json (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 Outdated finding(s) in Dependency Hygiene — start with FS.FluentUI.Charts.fsproj, TestGrounds.fsproj. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 recommendation-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 22 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 10 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 4 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
42 % of calls cross a namespace and 0 % 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)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,nuget). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,nuget), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 19 of the 23 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: Utils.fs↔TestCharts.fs 94%; TestGrounds.fs↔Utils.fs 79%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with Utils.fs, TestGrounds.fs. — One of this dimension's main actionable groups (2 issue-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
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
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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 1200 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.
- `src/FS.FluentUI.Charts/FS.FluentUI.Charts.fsproj` 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`. — src/FS.FluentUI.Charts/FS.FluentUI.Charts.fsproj:33
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
P6 · Release Hygiene
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Solid. |
| Architecture | 94% | Exemplary | Strongest area. |
| Maturity | 60% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 41% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- 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 — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 80 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend markup is written in a template language — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs), which the static markup model does not read — so accessibility is NOT MEASURED. No statically-readable markup was found at all; this is a blind spot in the scan, not a repository without a user interface.
- AC2 Forms & labels — Frontend markup is written in a template language — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs), which the static markup model does not read — so accessibility is NOT MEASURED. No statically-readable markup was found at all; this is a blind spot in the scan, not a repository without a user interface.
- AC3 Page structure — Frontend markup is written in a template language — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs), which the static markup model does not read — so accessibility is NOT MEASURED. No statically-readable markup was found at all; this is a blind spot in the scan, not a repository without a user interface.
- AC4 Keyboard semantics — Frontend markup is written in a template language — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs), which the static markup model does not read — so accessibility is NOT MEASURED. No statically-readable markup was found at all; this is a blind spot in the scan, not a repository without a user interface.
- AC5 ARIA correctness — Frontend markup is written in a template language — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs), which the static markup model does not read — so accessibility is NOT MEASURED. No statically-readable markup was found at all; this is a blind spot in the scan, not a repository without a user interface.
- AC6 Visual & motion safety — Frontend markup is written in a template language — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs), which the static markup model does not read — so accessibility is NOT MEASURED. No statically-readable markup was found at all; this is a blind spot in the scan, not a repository without a user interface.
- AC7 A11y enforcement — Frontend markup is written in a template language — 7 Feliz (F#) template file(s) carrying 156 markup element(s) (e.g. src/FS.FullCalendar/Props.fs, src/FS.FluentUI.V8toV9/FelizProps.fs, src/FS.FluentUI.Charts/Props.fs), which the static markup model does not read — so accessibility is NOT MEASURED. No statically-readable markup was found at all; this is a blind spot in the scan, not a repository without a user interface.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: Its F# is compiled by Fable to JavaScript, which runs on one event loop, so no two requests write a shared object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~4 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.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F#, JavaScript not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- 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.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 1950 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (1304 with fewer than two methods, 646 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 354 value object(s); 9 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 5 current-state document(s) make no claim of a kind M4 checks. 24 claim(s) of kinds M4 does not check were not checked (command argument 2, install 19, cd 3); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's F# code has 36,110 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — 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 — 5 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: Utils.fs ↔ TestCharts.fs src/FS.FluentUI.Charts/Utils.fs:1
- Boundary-crossing change coupling: TestGrounds.fs ↔ Utils.fs src/FS.FluentUI.TestGrounds/src/TestGrounds.fs:1
Serious — 33 finding(s)
- TooManyMethods: icon src/FS.FluentUI/FluentUI.fs:1192
- TooManyMethods: prop`1 src/FS.FluentUI.V8toV9/FelizProps.fs:16
- TooManyMethods: prop`1 src/FS.FluentUI/FelizProps.fs:16
- TooManyMethods: calendar src/FS.FullCalendar/Props.fs:15
- TooManyMethods: Fui src/FS.FluentUI/FluentUI.fs:214
- TooManyMethods: cartesianChart`1 src/FS.FluentUI.Charts/Props.fs:572
- TooManyMethods: datePicker src/FS.FluentUI/Props.fs:3349
- TooManyMethods: sNode src/FS.FluentUI.Charts/Props.fs:1344
- TooManyMethods: verticalStackedBarChart src/FS.FluentUI.Charts/Props.fs:3001
- TooManyMethods: virtualizer src/FS.FluentUI/Props2.fs:498
- TooManyMethods: event src/FS.FullCalendar/Props.fs:1753
- TooManyMethods: presenceMotionSlot src/FS.FluentUI/Props2.fs:3258
- TooManyMethods: text src/FS.FluentUI/FluentUI.fs:1156
- TooManyMethods: virtualizerScrollViewDynamic src/FS.FluentUI/Props2.fs:791
- TooManyMethods: timePicker src/FS.FluentUI/Props2.fs:2341
- FileTooLong: FS.FluentUI/FluentUI.fs src/FS.FluentUI/FluentUI.fs
- FileTooLong: FS.FluentUI/BundleIcons.fs src/FS.FluentUI/BundleIcons.fs
- FileTooLong: FS.FluentUI/Props2.fs src/FS.FluentUI/Props2.fs
- FileTooLong: FS.FluentUI/Props.fs src/FS.FluentUI/Props.fs
- FileTooLong: FS.FluentUI.Charts/Props.fs src/FS.FluentUI.Charts/Props.fs
- FileTooLong: FS.FullCalendar/Props.fs src/FS.FullCalendar/Props.fs
- FileTooLong: FS.FluentUI/Domain.fs src/FS.FluentUI/Domain.fs
- FileTooLong: FS.FluentUI.V8toV9/FelizProps.fs src/FS.FluentUI.V8toV9/FelizProps.fs
- FileTooLong: FS.FluentUI/FelizProps.fs src/FS.FluentUI/FelizProps.fs
- FileTooLong: FS.FullCalendar/Domain.fs src/FS.FullCalendar/Domain.fs
- inline-style-expand-shorthand.expandProperty (cyclomatic 17) src/FS.FluentUI/inline-style-expand-shorthand.js:483
- inline-style-expand-shorthand.expandWithMerge (cognitive 21) src/FS.FluentUI/inline-style-expand-shorthand.js:632
- inline-style-expand-shorthand.parseTextDecoration (cognitive 18) src/FS.FluentUI/inline-style-expand-shorthand.js:113
- inline-style-expand-shorthand.expand (cognitive 18) src/FS.FluentUI/inline-style-expand-shorthand.js:600
- inline-style-expand-shorthand.expandProperty (cognitive 17) src/FS.FluentUI/inline-style-expand-shorthand.js:483
- REDACTED
- No structured logging
- NuGet dependencies are not locked
Minor — 15 finding(s)
- Deprecated: querystring src/FS.FluentUI.TestGrounds/package-lock.json:6172
- Deprecated: querystring src/FS.FluentUI.TestGrounds/package-lock.json:6531
- Deprecated: uuid src/FS.FluentUI.TestGrounds/package-lock.json:6899
- Outdated: FSharp.Core src/FS.FluentUI.Charts/FS.FluentUI.Charts.fsproj:33
- Outdated: Feliz.UseElmish src/FS.FluentUI.TestGrounds/src/TestGrounds.fsproj:46
- Outdated (npm): js-tokens
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation src/FS.FluentUI.Charts/FS.FluentUI.Charts.fsproj:33
Minor — 81 finding(s)
- Outdated (npm): @babel/runtime
- Outdated (npm): @ctrl/tinycolor
- Outdated (npm): @emotion/hash
- Outdated (npm): @floating-ui/core
- Outdated (npm): @floating-ui/dom
- Outdated (npm): @floating-ui/utils
- Outdated (npm): @fluentui/chart-utilities
- Outdated (npm): @fluentui/fluent2-theme
- Outdated (npm): @fluentui/font-icons-mdl2
- Outdated (npm): @fluentui/foundation-legacy
- Outdated (npm): @fluentui/merge-styles
- Outdated (npm): @fluentui/react
- Outdated (npm): @fluentui/react-breadcrumb
- Outdated (npm): @fluentui/react-button
- Outdated (npm): @fluentui/react-carousel
- Outdated (npm): @fluentui/react-charts
- Outdated (npm): @fluentui/react-color-picker
- Outdated (npm): @fluentui/react-components
- Outdated (npm): @fluentui/react-focus
- Outdated (npm): @fluentui/react-hooks
- Outdated (npm): @fluentui/react-icons
- Outdated (npm): @fluentui/react-menu
- Outdated (npm): @fluentui/react-message-bar
- Outdated (npm): @fluentui/react-migration-v8-v9
- Outdated (npm): @fluentui/react-nav
- Outdated: Fable.Core
- Outdated: Feliz
- Outdated: Feliz.CompilerPlugins
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-facda422d0e04978bee5e74a51749da7/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-facda422d0e04978bee5e74a51749da7/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list FS.FluentUI.sln package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| 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 . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |